Bug 82105

Summary: Security Level Configuration Tool does not show/save correct values
Product: [Retired] Red Hat Linux Reporter: Magesh Rangaramanujam <rangma>
Component: redhat-config-securitylevelAssignee: Brent Fox <bfox>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Magesh Rangaramanujam 2003-01-17 16:24:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 
1.0.3705)

Description of problem:
I set the security level to "no firwall", save it and close the window. When I 
open the security level configuration tool again, it show maximum security and 
not the settings I selected previously.

Also, it seems to save settings that are not chosen. 

What I experienced:
Telnet was working fine. I viewed the security level a couple of times, each 
time setting the level to 'no firewall'. I did not touch the machine for a 
couple of days. Then I tried to telnet into the machine, it kept saying 
connection refused. 
I checked 'iptables -L' and it has stuff I did not choose.


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


How reproducible:
Didn't try

Steps to Reproduce:
1. open the security level configuration gui
2. make changes
3. close it
4. repeat steps 1-3 several times
    

Actual Results:  saved values not shown when gui is opened next.

Expected Results:  should show actual saved values.

Additional info:

Comment 1 Harald Hoyer 2003-01-20 10:53:37 UTC
assigning to correct component

Comment 2 Brent Fox 2003-01-20 16:01:34 UTC

*** This bug has been marked as a duplicate of 67500 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:51:13 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.