Bug 82105 - Security Level Configuration Tool does not show/save correct values
Security Level Configuration Tool does not show/save correct values
Status: CLOSED DUPLICATE of bug 67500
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-securitylevel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-01-17 11:24 EST by Magesh Rangaramanujam
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:51:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

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

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 05:53:37 EST
assigning to correct component
Comment 2 Brent Fox 2003-01-20 11:01:34 EST

*** This bug has been marked as a duplicate of 67500 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:13 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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