Bug 26385 - Bizarre behavior of /etc/ftphosts
Summary: Bizarre behavior of /etc/ftphosts
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: wu-ftpd
Version: 7.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-07 00:56 UTC by Christian Lepine
Modified: 2007-04-18 16:31 UTC (History)
0 users

Clone Of:
Last Closed: 2001-03-12 22:32:49 UTC

Attachments (Terms of Use)

Description Christian Lepine 2001-02-07 00:56:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [fr] (X11; U; Linux 2.2.16-22 i686)

The man page of ftphosts says that when I use deny username addrglob, hosts
maching addrglob logging in as username will be deny.
Actually, the username is always deny even if he is from another addrglob.
I have try :
deny tux


deny tux *.maison

And I always get a deny even if the user tux is comming from another
address or domain ???? 

Reproducible: Always
Steps to Reproduce:
1. enter a deny directive for a user maching an address in /etc/ftphosts
(deny tux
2. Try to connect from another address but with that username (ncftp -u tux
ftp.maison) note that the client address is not 192.168.100.

Actual Results:  It won't connect

Expected Results:  The user tux is not comming from address
so he should be able to connect

Comment 1 Karsten Hopp 2001-02-07 14:32:01 UTC
verified even with IPs of xx.xx.xx.xx/mask. Regardless of the IP, the access
for this user will be denied. (wu-ftpd-2.6.1-12)

Comment 2 Bernhard Rosenkraenzer 2001-02-07 14:37:13 UTC
Yes, wu-ftpd's algorithm for determining these things is ultimately broken
and needs a rewrite. pHtmp is ALWAYS NULL if a matching entry is found
but does not apply.
I'll fix this later today.

Comment 3 WU-FTPD Development Group 2001-03-12 22:32:46 UTC
Index: doc/ftphosts.5
RCS file: /cvsroot/wu-ftpd/doc/ftphosts.5,v
retrieving revision 1.6
diff -r1.6 ftphosts.5
> The last rule which matches is the default rule.  So, to allow a user to login
> from anywhere _except_ the listed hosts, you need both allow and deny rules.
> The following example denies the user hacked from logging in from the host
>, but allows login from all other hosts.
> deny hacked
> allow hacked *

Please close this ricket.

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