Date: Mon, 18 May 2015 14:22:13 +0100 From: Paul Macdonald <paul@ifdnrg.com> To: freebsd-ports@freebsd.org Subject: Re: Proftpd bug, chroot does not allow for access to or creation of folders named 'lib' Message-ID: <5559E785.1010602@ifdnrg.com> In-Reply-To: <20150330135318.GI62590@home.opsec.eu> References: <551460C0.3060609@ifdnrg.com> <55195013.3090509@quip.cz> <551950EC.2030205@ifdnrg.com> <20150330135318.GI62590@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> I can confirm this problem on FreeBSD 8.4-RELEASE i386 with >>> proftpd-1.3.5_2 >>> >>> Is some patch available to fix this? (I cannot disable DefaultChroot) >>> >> a bug report has been filed. >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198938 > I've updated the PR with some short info what I found. Basically, > there's a special case in src/fsio.c which explicitly denies > writing to /etc and /lib in the chroot-case, refering to 3 year > old AUSCERT warnings for proftpd with FreeBSD. > > Someone needs to check whether those warnings still apply to current-day > proftpd and freebsd. I'd updated the PR but just in case this is of use to the list the workaround is simply to create a parent folder for your ftp root, so as viewed by proftpd /etc/ would become /parent/etc Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5559E785.1010602>