Bug 104910 – iptables default rules

Bug 104910 - iptables default rules

Summary:	iptables default rules

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux Beta
Classification:	Retired
Component:	redhat-config-securitylevel (Show other bugs)
Sub Component:
Version:	beta3
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Brent Fox
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:	Security

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-09-23 10:48 EDT by JBowes
Modified:	2007-04-18 12:57 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-12-19 08:22:13 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description JBowes 2003-09-23 10:48:46 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Epiphany/0.8.0

Description of problem:
The default policy after using lokkit for a basic firewall are set to accept.
Having used lokkit in versions 8 and 9 previously this problem was not existing.

Version-Release number of selected component (if applicable):
iptables-1.2.8-7.1

How reproducible:
Always

Steps to Reproduce:
1.launch lokkit
2.select customize, add rules and close lokkit
3.List default policy and chains
    

Actual Results:  Policy is always set to allow - no matter what

Expected Results:  The default should been to only allow in the traffic I
specified - ssh.

Additional info:

Comment 1 Bill Nottingham 2003-09-23 11:40:59 EDT

What does iptables -L say?

Comment 2 Brent Fox 2003-10-14 19:25:50 EDT

JBowes: ping?

Comment 3 Mark J. Cox (Product Security) 2003-12-19 08:22:13 EST

No response, marking as closed.  Please reopen if you have more
information that can help us diagnose this problem.

Note You need to log in before you can comment on or make changes to this bug.