|Summary:||lokkit's relay test ends in a strange way|
|Product:||[Retired] Red Hat Linux||Reporter:||Joshua Jensen <joshua>|
|Component:||gnome-lokkit||Assignee:||Bill Nottingham <notting>|
|Status:||CLOSED RAWHIDE||QA Contact:||Ben Levenson <benl>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2003-08-04 21:07:23 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Joshua Jensen 2002-07-29 19:04:24 UTC
Description of Problem: I'm filing under iptables, because I can't find a lokkit component. When I run lokkit graphically, and I choose to test for an open relay... the test proceeds, but then ends with an "EOF. Finished" error. I think this means that everything is OK, but I really should not have to guess. Version-Release number of selected component (if applicable): lokkit-0.50-14 How Reproducible: run lokkit as described
Comment 1 Bill Nottingham 2002-07-30 03:43:24 UTC
AFAIK, that's the way it's supposed to work.
Comment 2 Joshua Jensen 2002-07-31 21:05:04 UTC
You're kidding, right?!! Users are supposed to know that "EOF. Finished" means "you don't have an open relay"? Surly we should consider this bad UI, that could easily be fixed by printing a different string.
Comment 3 Bill Nottingham 2003-08-04 21:07:23 UTC
gnome-lokkit frontend removed as of redhat-config-securitylevel-1.2.0-1.