Bug 70055 - lokkit's relay test ends in a strange way
lokkit's relay test ends in a strange way
Product: Red Hat Linux
Classification: Retired
Component: gnome-lokkit (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-07-29 15:04 EDT by Joshua Jensen
Modified: 2014-03-16 22:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-04 17:07:23 EDT
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 Joshua Jensen 2002-07-29 15:04:24 EDT
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):


How Reproducible:

run lokkit as described
Comment 1 Bill Nottingham 2002-07-29 23:43:24 EDT
AFAIK, that's the way it's supposed to work.
Comment 2 Joshua Jensen 2002-07-31 17:05:04 EDT
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 17:07:23 EDT
gnome-lokkit frontend removed as of redhat-config-securitylevel-1.2.0-1.

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