Date: Sat, 23 Jun 2012 17:35:45 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Garance A Drosehn <gad@FreeBSD.org> Cc: freebsd-security@FreeBSD.org, "Julian H. Stacey" <jhs@berklix.com> Subject: Re: / owned by bin causes sshd to complain bad ownership Message-ID: <86r4t6yram.fsf@ds4.des.no> In-Reply-To: <4FE4B57C.1040701@FreeBSD.org> (Garance A. Drosehn's message of "Fri, 22 Jun 2012 14:12:12 -0400") References: <201206221715.q5MHFPJW052099@fire.js.berklix.net> <4FE4B57C.1040701@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosehn <gad@FreeBSD.org> writes: > At one time I read that having directories/files owned by root was a > security benefit when considering the -maproot=3D<x> for NFS exports. > All unix systems recognize UID=3D0 means root, and there is no other > UID which all unix systems agree on. Disclaimer: I rarely use NFS, > so I don't really pay attention to the details. I may have the wrong > idea for what the advantage is, but it was some kind of connection > with UID=3D0 and NFS exports or imports. -maproot=3Dfoo means that requests coming from root on the client are treated as if the came from the user "foo" instead. If binaries are owned by bin, root on the client can su to bin and modify them. If they are owned by root and the server maps root to an unprivileged user (e.g. "nobody"), root on the client can't touch them. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86r4t6yram.fsf>