Red Hat Bugzilla – Bug 174281
Too many other ports listed causes Configuration window load failure in KDE
Last modified: 2007-11-30 17:11:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.0.6-1.2.fc4 Firefox/1.0.6
Description of problem:
I noticed that when I enter too many ports into the Other ports field of the Security Level Configuration window(becuase I cannot enter a range, I tried to enter each individual port of that range) and then press ok, the next time I try to open the Security Level Configuration window it fails to open. When running system-config-securitylevel from the shell, I can get into a console version of this window. From this console version I see that the complete list of Other ports I supplied to the Security Level Configuration window was truncated prematurely. After removing all the ports I had entered before, and trying the Security Level Configuration window, it worked normally as before. Obviously the number of ports which can be entered in this field is finite, but a user should be able to still access the Security Level Configuration no matter what values are entered in this field.
Version-Release number of selected component (if applicable):
Version off stable FC4 install disks
Steps to Reproduce:
1.Enter 30 different Ports in the Other Ports field of the Security Level Configuration window
3.Try to reopen the Security Level Configuration window through the menu by selecting: System Settings->Security Level
Actual Results: Root Authentication was asked for.
After root authentication was given nothing happened
and Security Level Configuration window would never open.
Expected Results: The Security Level Configuration window should open.
If too many values are entered into the Other ports field, then it would be nice to be informed of that and allowed to be able to correct it from the Security Level Configuration window.
The problem here is that each port you specify gets passed to lokkit as a
command line argument of the form "--port=<port>:<proto>". So we're running
into the command line argument length limit, I believe.
The real fix will be range support in s-c-securitylevel (see bug 164187).
However, there's probably something else worth investigating here as to why the
gui just doesn't even start.