Linux NFS development
 help / color / mirror / Atom feed
From: Kapeller Rene PSI <rene.kapeller@psi.ch>
To: nfs@lists.sourceforge.net
Subject: root_squash problem
Date: Fri, 20 Sep 2002 16:42:33 +0200	[thread overview]
Message-ID: <3D8B33D9.9050006@psi.ch> (raw)

We are running RedHat-6.2 on a file server.
The system is now up for more than 200 days and it's main function is to 
provide nfs service to almost 100 clients on two different networks.

The system has been upgraded as follows:
- nfs-utils-0.3.1-0.6.x.1
- kernel-2.4.17

I have a rather large number of exports entries for different directories.
However, a few clients only have write access as 'root' to the nfs path 
as you see below.

[root]# grep no_root_squash /proc/fs/nfs/exports
/export/install 172.19.78.74(rw,no_root_squash,async,wdelay) # 172.19.78.74
/export/cern    pc2376.psi.ch(rw,no_root_squash,async,wdelay) # 
(129.129.70.42)
/export/csa     129.129.72.97(rw,no_root_squash,async,wdelay) # 
129.129.72.97
/export/exchange        129.129.72.97(rw,no_root_squash,async,wdelay) # 
129.129.72.97

Today I was very surprised (and worried), when I have noticed that 
'root' from any other client can also write to the above nfs directories.

Needles to say, that this is a terrible security whole in our environment.

Thanks for any hint/help
Rene



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2002-09-20 14:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D8B33D9.9050006@psi.ch \
    --to=rene.kapeller@psi.ch \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox