Bug 216192 - Firewall port 5222 overwrite
Summary: Firewall port 5222 overwrite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-17 18:30 UTC by Teri Waters
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-17 18:37:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Teri Waters 2006-11-17 18:30:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1)

Description of problem:
Not all the port changes done with the GUI are picked back up by the GUI on subsequent edits. The overwrite then blows the omitted ports away. For whatever reason, the GUI refuses to recognize 5222 when you reopen it for edit. It's like it's not there and when you hit OK, it isn't. It gets overridden and thus blocked.



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


How reproducible:
Always


Steps to Reproduce:
1. Enable firewall from GUI Security Level Configuration
2. Enable https and SSL (although this is irrelevant).
3. Select other ports
4. Add 5222 and perhaps others like 5901 for example.
5. Ok
6. Reenter firewall GUI "security level configuration"
7. Note port 5222 is no longer there. If you do nothing and exit. The config is overlaid and port 5222 no longer exists and is subsequently blocked.
8. The only workaround is to enter 5222 as an added other port each time you enter the GUI.

Actual Results:
Reenter firewall GUI "security level configuration". 
Note port 5222 is no longer there. If you do nothing and exit. The config is overlaid and port 5222 no longer exists and is subsequently blocked.

Expected Results:
The port should not disappear it should remain active until you remove it.

Additional info:

Comment 1 Chris Lumens 2006-11-17 18:37:35 UTC
This is fixed in 1.6.16-3, which was released as an update to FC5.


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