Date: Thu, 27 Aug 2015 15:19:04 +0200 From: Borja Marcos <borjam@sarenet.es> To: Mike Tancsa <mike@sentex.net> Cc: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-15:22.openssh Message-ID: <EF0C7D98-5561-47DB-9AAB-1046C6638F7C@sarenet.es> In-Reply-To: <55DF0BBD.1080206@sentex.net> References: <20150825212749.C154016C9@freefall.freebsd.org> <55DE0E74.4040000@sentex.net> <86h9nlqjmn.fsf@nine.des.no> <55DF0BBD.1080206@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 27, 2015, at 3:08 PM, Mike Tancsa wrote: > On 8/27/2015 3:24 AM, Dag-Erling Sm=F8rgrav wrote: > For the latter two, I am trying to understand in the context of a = shared > hosting system. Could one user with sftp access to their own directory > use these bugs to gain access to another user's account ? Straghtforward Unix permissions aren't really suited to such an = application. You need everything to be world readable by an unprivileged WWW server.=20 In such a setup we were successful by using a combination of mac/biba = for integrity, ugidfw for effective user separation, and removing all the setuid permissions from = the system. Otherwise, a non-chrooted hosting user will have at least read only = access to the neighbors. Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EF0C7D98-5561-47DB-9AAB-1046C6638F7C>