Bug 249430 - hosts.allow netmask broken for localhost
Summary: hosts.allow netmask broken for localhost
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: tcp_wrappers (Show other bugs)
(Show other bugs)
Version: 4.5
Hardware: x86_64 Linux
Target Milestone: ---
: ---
Assignee: Petr Lautrbach
QA Contact: qe-baseos-daemons
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-24 17:18 UTC by tsc5yc
Modified: 2012-06-20 13:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 13:22:55 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description tsc5yc 2007-07-24 17:18:50 UTC
Description of problem:
hosts.allow net/mask pattern does not work as expected, at least while using

Version-Release number of selected component (if applicable):
# rpm -qa | grep tcp_wrappers

note: twice?

How reproducible:
Every time

Steps to Reproduce:
1. add "ALL: ALL" to /etc/hosts.deny
2. add "sendmail:" to /etc/hosts.allow
3. #chkconfig sendmail on; service sendmail start
4. #echo "testing" | mail -s "Test" me@mymail.com
5. check /var/log/maillog
Actual results:
Jul 24 11:48:38 __ sendmail[21230]: ____________: tcpwrappers (___________, rejection

Expected results:
tcpwrappers to allow sendmail:

Additional info:
works, but
does NOT work either
if 126/254 succeeds, why does neither 127/255 nor 126/255 work?

Comment 2 Tomas Janousek 2007-07-25 13:43:07 UTC
The fix is really simple, but won't make it to 4.6. Please, use just ""

Comment 3 RHEL Product and Program Management 2008-02-01 19:04:39 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 4 Jiri Pallich 2012-06-20 13:22:55 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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