If you mean from "if they have physical access to the box and are
determined, they'll get root anyway" you mean exploit some unpatched
service on the system -- then you may aswell forget about and type of NFS
"squash" option altogether! ...as we are in a different territory now. 
See other securityfocus.com mailing lists on that one! ;-)

The "sqash" options solves alot of problems, but to answer the first
question fully (as opposed to my half-assed original!) then securing the
network and utilising some other type of NFS/Directory service is the
answer.

NFS/NIS _or_ Security.  AFAIK, its always been the two options.

The problem in the first place was to stop normal users su'ing to root and
then being able to write files.  Solved by root_squash.
But then of course, that person can su - user and then write files.

So the problem really resolves around a way of protecting root on the
local system AND still provide NFS-like mounting of remote directories.
These aren't answered by using NIS and NFS alone.

Kev


> In addition to the other examples people have given, think of a lab
> environment where untrusted users aren't given root... but of course, if
>  they have physical access to the box and are determined, they'll get
> root  anyway.  I think this discussion is helpful; too many people think
> root  squashing solves more problems than it really does.
>



-- 
Kevin Jackson
Systems Administrator                        Locate, Enquire, Empower
GenaWare Limited                              www.genaware.com




------------------------------------------------------------------------
PRIVILEGED - PRIVATE AND CONFIDENTIAL

This email and any files transmitted with it are intended solely for the
use of the addressee(s) and may contain information which is
confidential or privileged. If you receive this email and you are not
the addressee (or responsible for delivery of the email to the
addressee), please disregard the contents of the email, delete the email
and notify the author immediately.

Before opening or using any attachments, please scan them for viruses
and defects. We do not accept any liability for loss or damage, which
may arise from your receipt of this e-mail. Our liability is limited to
re-supplying any affected attachments.

Reply via email to