Hi everyone !

Right now I can’t decide wich one is the most versatile and fit my personal needs, so I’m looking into your personal experience with each one of them, if you mind sharing your experience.

It’s mostly for secure shared volumes containing ebooks and media storage/files on my home network. Adding some security into the mix even tough I actually don’t need it (mostly for learning process).

More precisely how difficult is the NFS configuration with kerberos? Is it actually useful? Never used kerberos and have no idea how it works, so it’s a very much new tech on my side.

I would really apreciate some indepth personal experience and why you would considere one over another !

Thank you !

  • acockworkorange
    1·
    7 months ago

    How do I set permissions up with NFS? Do I have to have the same uids and gids on both server and clients?

    • giloronfoo@beehaw.org
      1·
      7 months ago

      I think that’s what the kerberos is there to solve. I’ve heard that it isn’t that bad to set up. I haven’t tried and just stuck with SMB.

      • acockworkorange
        1·
        7 months ago

        Yeah, I just wanted to have something mounted at boot on my Linux box from my NAS. Looks like it’s possible with SMB, I just need to figure out how to match the users on my machine with the ones on my server.

    • Spectranox@lemmy.dbzer0.comEnglish
      1·
      7 months ago

      In my experience, just making sure the directory you’re sharing is owned by nobody:nogroup is enough.

      sudo chown -R nobody:nogroup /path/to/nfs

      • atzanteol@sh.itjust.worksEnglish
        1·
        7 months ago

        Ohh, no - you don’t want to do that. Why would you do that?

        NFS without kerberos uses the UIDs of the remote users to determine access to files on the server. It’s very insecure since the client systems can use whatever UIDs they want. It’s why NFS has a “squash root” option which blocks any remote system from using UID 0. Kerberos allows users to authenticate so that the server knows who they are on the local system rather than trusting the remote system.

        Changing ownership to “nobody” doesn’t give anyone access - it just sets the owner to the “nobody” user. You would need to “chmod” to give read/write permissions.

        • Spectranox@lemmy.dbzer0.comEnglish
          1·
          7 months ago

          I’m not an expert with this stuff, I just do whatever works. This works, so I do it and when people ask me or just in general how to do it this is what I tell them. Most of the guides I’ve come across, including one from DigitalOcean, recommends doing this.

          • atzanteol@sh.itjust.worksEnglish
            1·
            7 months ago

            Ah - that’s the root-squashing I was mentioning. Root is translated to “nobody” on the server. If you’re not using the root user or if you’ve set “no_root_squash” then you don’t need/want to do that.