<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: root_squash in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415134#M82067</link>
    <description>Since this has already been answered, I can tell you what it's not. It definitely is not a vegetable eaten during NFS file transfers.</description>
    <pubDate>Thu, 07 May 2009 17:54:10 GMT</pubDate>
    <dc:creator>Court Campbell</dc:creator>
    <dc:date>2009-05-07T17:54:10Z</dc:date>
    <item>
      <title>root_squash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415129#M82062</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;can someone explain pls root_squash parameter from Network File System (NFS)?</description>
      <pubDate>Thu, 07 May 2009 11:30:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415129#M82062</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2009-05-07T11:30:20Z</dc:date>
    </item>
    <item>
      <title>Re: root_squash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415130#M82063</link>
      <description>Hi Chris,&lt;BR /&gt;&lt;BR /&gt;IMHO this parameter determines whether root user is allowed to access a NFS-shared filesystem.&lt;BR /&gt;&lt;BR /&gt;J.</description>
      <pubDate>Thu, 07 May 2009 11:48:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415130#M82063</guid>
      <dc:creator>Jozef_Novak</dc:creator>
      <dc:date>2009-05-07T11:48:17Z</dc:date>
    </item>
    <item>
      <title>Re: root_squash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415131#M82064</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;root_squash - Requests from root clients are mapped to the nobody user and group ID so they will only have file privileges associated with other&lt;BR /&gt;&lt;BR /&gt;Please also check below for more details info&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.linuxsecurity.com/content/view/117705/171/" target="_blank"&gt;http://www.linuxsecurity.com/content/view/117705/171/&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 07 May 2009 12:34:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415131#M82064</guid>
      <dc:creator>avizen9</dc:creator>
      <dc:date>2009-05-07T12:34:11Z</dc:date>
    </item>
    <item>
      <title>Re: root_squash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415132#M82065</link>
      <description>my /etc/exports from nfs server is:&lt;BR /&gt;&lt;BR /&gt;/nfs/box    192.168.0.0/24(rw,no_wdelay,root_squash,insecure_locks,anonuid=1025,anongid=100)&lt;BR /&gt;&lt;BR /&gt;I mount from the nfs client without problems.&lt;BR /&gt;But if I have in /etc/exports root_squash on the server than I cannot write via nfs client on the nfs server.&lt;BR /&gt;If I change to no_root_squash then I can write.&lt;BR /&gt;What's the problem?</description>
      <pubDate>Thu, 07 May 2009 13:20:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415132#M82065</guid>
      <dc:creator>'chris'</dc:creator>
      <dc:date>2009-05-07T13:20:00Z</dc:date>
    </item>
    <item>
      <title>Re: root_squash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415133#M82066</link>
      <description>If root_squash is enabled and the root user of the NFS client host is accessing the NFS-mounted filesystem, the NFS server will re-map the root's identity to "nobody" (traditional), "nfsnobody" (on some Linux distributions and/or types of Unix) or the user identified with the anonuid and anongid options. In other words, the client-side root privilege is "squashed" away. Only the root of the NFS server has true root-level access on the shared disk.&lt;BR /&gt;&lt;BR /&gt;This is a security feature. If the NFS server shares a filesystem that contains executables (e.g. /usr) and an unauthorized person gets root access on the NFS client host, without the root_squash feature the user could replace any binary in the server's filesystem with a SUID root binary of his/her own design. &lt;BR /&gt;If s/he can then make any user (or even a cron job) on the server to run his/her tampered executable, that executable can easily give him/her unauthorized root access on the server too.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Thu, 07 May 2009 17:12:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415133#M82066</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-05-07T17:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: root_squash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415134#M82067</link>
      <description>Since this has already been answered, I can tell you what it's not. It definitely is not a vegetable eaten during NFS file transfers.</description>
      <pubDate>Thu, 07 May 2009 17:54:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415134#M82067</guid>
      <dc:creator>Court Campbell</dc:creator>
      <dc:date>2009-05-07T17:54:10Z</dc:date>
    </item>
    <item>
      <title>Re: root_squash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415135#M82068</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;My understanding is root_squash controls whether root can mount an NFS share as root or not.&lt;BR /&gt;&lt;BR /&gt;By default as a security measure you can not mount an NFS share remotely as root. The reason is the local sharing system can not guarantee or know the security level of the client.&lt;BR /&gt;&lt;BR /&gt;An insecure host could mount a share and the sharing system can be exploited.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 07 May 2009 23:39:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415135#M82068</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-05-07T23:39:15Z</dc:date>
    </item>
    <item>
      <title>Re: root_squash</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415136#M82069</link>
      <description>SEP, Matti is actually correct.</description>
      <pubDate>Mon, 11 May 2009 14:31:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-squash/m-p/4415136#M82069</guid>
      <dc:creator>Court Campbell</dc:creator>
      <dc:date>2009-05-11T14:31:48Z</dc:date>
    </item>
  </channel>
</rss>

