> If you want to prevent apps from reading zoneinfo files that a user > can write and read files a user can write, you will loose. > > Why are you setting up the chroot with content a user can write too? > If you simply prevent him from writing to /usr/share, won't that > solve > the problem? Not really. Because, in fact, the user, when chrooted, is writing to /home/user/usr/share/zoneinfo/. I've suggested a different file context for /home/(.*)/usr/share/zoneinfo(/.*) in vsftpd policy module. But I don't think this will be necessary due to the recent findings about vsftpd.
-- Ramon de C Valle / Red Hat Security Response Team _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
