Bug 503588

Description of problem:
Validation of the "Other Ports" in system-config-securitylevel is broken. When a port is entered, it's service name is derived and then added to the list. So in case of service names with hypens, they are assumed to be port ranges and are split and the individual sections are found to be invalid.

This way, even when such ports are added, they are not visible in the list. You can see that the rules have been added with iptables-save. Subsequent changes to ports in system-config-securitylevel will remove the rules added for those earlier ports.

Version-Release number of selected component (if applicable):
system-config-securitylevel-1.6.29.1-2.1.el5

How reproducible:
Always

Steps to Reproduce:
1. Start system-config-securitylevel
2. Click on the "Other Ports" section
3. Click on "Add"
4. Enter 1156 as port.  Leave protocol as tcp
5. Press OK
6. Press Apply and Ok to close
7. iptables-save
  
Actual results:
The firewall rule for 1156 has been applied but it is not seen as added in system-config-securitylevel

Expected results:
1156 should be visible in system-config-securitylevel as iascontrol-oms

Additional info:
s-c-securitylevel 1.6.30 fixes this condition, but at the same time this version does not have any real validation at all. The rule for validation is effectively, "It should be a number, range of numbers or characters," but there is no validation of whether the characters represent a valid service name.