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 !

  • tburkhol@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    If you’re going to have any non-linux clients, samba will be an order of magnitude easier. MacOS handles nfs pretty well, but Windows just wants SMB

    • wvstolzing@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      macOS switched from AFS to samba for file sharing & time machine backups a while ago; it’s been a while since I had first-hand experience setting up a Mac, but based on that fact I’m pretty sure samba is more straightforward to use. … it annoyingly mangles unix file ownership, & permissions though, as mentioned above in https://lemmy.ml/comment/10204431

    • DefederateLemmyMl@feddit.nl
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      You don’t have to choose just one though. It’s perfectly ok to share a directory via Samba for Windows clients and share the same directory again with NFS for Linux clients.

  • lemmyreader@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago
    • NFS : historically insecure by default. Don’t know about Kerberos making it secure but Kerberos does not look easy to configure.

    • sshfs : probably most easy to setup. Can be confusing with ownership and permissions sometimes.

    • Samba : solid but has a learning curve, even for a simple setup. For example, for a standalone Samba server omitting the Active Directory part, you need to know that in order to create a Samba user you must first have created a local user with the same username.

    https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server

    • TCB13@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      sshfs : probably most easy to setup. Can be confusing with ownership and permissions sometimes.

      And the worst option if you have Windows clients.

      • rzr@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago

        I am wondering if someone can recommend any libre sshfs client for windows7+ preferably that could be installed as a portable app ?