Bug 20567

Summary: What is wrong - docs or xinetd - trouble with /etc/hosts.allow
Product: [Retired] Red Hat Linux Reporter: Milan Kerslager <milan.kerslager>
Component: xinetdAssignee: Trond Eivind Glomsrxd <teg>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-11-09 19:24:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milan Kerslager 2000-11-09 10:01:56 UTC
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 
IMAPS.

Comment 1 Tim Waugh 2000-11-09 12:53:04 UTC
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 19:24:29 UTC
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 19:51:18 UTC
Fixed in xinetd-2.1.8.9pre12-3, which eventually will show up in Rawhide.