Red Hat Bugzilla – Bug 26385
Bizarre behavior of /etc/ftphosts
Last modified: 2007-04-18 12:31:15 EDT
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 192.168.1.100
deny tux *.maison
And I always get a deny even if the user tux is comming from another
address or domain ????
Steps to Reproduce:
1. enter a deny directive for a user maching an address in /etc/ftphosts
(deny tux 192.168.1.100)
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 192.168.1.100
so he should be able to connect
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)
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.
RCS file: /cvsroot/wu-ftpd/doc/ftphosts.5,v
retrieving revision 1.6
diff -r1.6 ftphosts.5
> NOTE VERY CAREFULLY:
> 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
> 10.1.2.3, but allows login from all other hosts.
> deny hacked 10.1.2.3
> allow hacked *
Please close this ricket.