Date: Tue, 3 Feb 2015 10:49:08 -0600 From: "Joshua J. Drake" <oss-sec@...p.org> To: oss-security@...ts.openwall.com Subject: Re: vsftpd problem in deny_hosts Maybe it would be prudent to canonicalize the path and match against that instead. What are your thoughts? PS. sorry for the top post Joshua On Tue, Feb 03, 2015 at 07:29:15AM -0800, Chris Evans wrote: > > The "variety of names" clause above is for situations like /home vs. > /./home/ vs. /../home vs. /.././../home etc. > > This option is just a regex-like match against the raw FTP argument. So, > I'm not sure it's possible to use deny_file=/home/*. Even if that were > tweaked to deny_file=*/home/*, it would only work if the initial directory > were set _outside_ /home -- if it wasn't, RETR some/relative/path would > work because /home/ does not appear in the string. > > Perhaps the wording in the man page is not strong enough, or not detailed > enough about implications, or I should just remove it? Suggestions welcome. [ CONTENT OF TYPE application/pgp-signature SKIPPED ]
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Powered by Openwall GNU/*/Linux - Powered by OpenVZ