Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 20567 - What is wrong - docs or xinetd - trouble with /etc/hosts.allow
What is wrong - docs or xinetd - trouble with /etc/hosts.allow
Product: Red Hat Linux
Classification: Retired
Component: xinetd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2000-11-09 05:01 EST by Milan Kerslager
Modified: 2007-04-18 12:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-11-09 14:24:32 EST
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 Milan Kerslager 2000-11-09 05:01:56 EST
When I modified /etc/hosts.allow i read the xinetd doc:

With this option (compiling option --with-libwrap) turned on, xinetd will 
first look at your /etc/hosts.{allow|deny} files, then if access is 
granted, it goes through xinetd's internal access control mechanisms.  
Note that xinetd passes the service name, *not* the server name to libwrap

But services in /etc/hosts.allow depend on server name and *not* on 
service name. This is bad as I can't set up different lines for SPOP and 
Comment 1 Tim Waugh 2000-11-09 07:53:04 EST
This is a documentation problem.  The server name is used, since that's what's
always been used in those files.
Comment 2 Trond Eivind Glomsrxd 2000-11-09 14:24:29 EST
The behaviour in xinetd was changed to match the old behaviour, but the
documentation wasn't changed... will fix.
Comment 3 Trond Eivind Glomsrxd 2000-11-09 14:51:18 EST
Fixed in xinetd-, which eventually will show up in Rawhide.

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