[Bug 577165] Re: Typo in etc/init/vsftpd.conf
Imre Gergely
gimre at narancs.net
Mon Dec 13 21:53:35 GMT 2010
** Description changed:
Binary package hint: vsftpd
- [ -d /var/run/vsftpd/emply ] || install -m 755 -o root -g root -d
+ [ -d /var/run/vsftpd/emply ] || install -m 755 -o root -g root -d
/var/run/vsftpd/empty
Obviously "emply" is not the same as "empty".
+
+ IMPACT: very low. vsftpd needs an empty directory for chroot environment,
+ according to comments in vsftpd.conf:
+
+ # This option should be the name of a directory which is empty. Also, the
+ # directory should not be writable by the ftp user. This directory is used
+ # as a secure chroot() jail at times vsftpd does not require filesystem
+ # access.
+ secure_chroot_dir=/var/run/vsftpd/empty
+
+ The upstart script in /etc/init/vsfptd.conf checks for this directory and
+ it created it with the proper permissions IF there is no such directory.
+ As the script in Lucid has a typo in the checking part, the condition is
+ never true and the directory gets created no matter what.
+
+ This is fixed in Maverick. Patch is attached for Lucid.
+
+ TEST CASE:
+
+ There is no visible problem to reproduce. See IMPACT above.
+
+ Without the patch the directory creation happens every time, with the patch
+ it happens ONLY if the directory does not exist.
+
+ REGRESSION POTENTIAL: low/none.
+
+ NOTE: as this is not a serious bug, it should be SRU'd together with
+ #648202 and/or #629234 .
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in ubuntu.
https://bugs.launchpad.net/bugs/577165
Title:
Typo in etc/init/vsftpd.conf
More information about the Ubuntu-server-bugs
mailing list