Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Thank you. We are using SFTP/SSHFS currently. But many people say we shouldn't be as it isn't designed for shared access to a fileserver. NFSv4 in Kerberos mode interests us, but we heard that setting up Kerberos is very challenging. Next up for consideration is FreeIPA based on this and other articles: happyassassin.net/2014/09/07/freeipa-for-amateurs-why But before implementing a FreeIPA+NFS stack we wanted to explore any and all potentially simpler options. Everything seems to point back to NFSv4 + Kerberos with FreeIPA. Commented Feb 2, 2018 at 9:01
  • Samba may be an option for you as well if you don't want to go the full LDAP/Kerberos route (setting up a standalone server would likely be sufficient.) Commented Feb 2, 2018 at 9:13
  • Yes, I agree that Samba4 is an option for us. But @colt pointed out this complication "Due to limitations present when provisioning the AD DC role, Samba recommends that you not use a Samba domain controller as a file server" Commented Feb 2, 2018 at 9:25
  • Going full domain mode is almost certainly overkill for your network unless you have huge numbers of users! I'd just use the standalone server mode and change passwords on the server when needed. If you're using a desktop environment like GNOME or KDE, it can handle the password storing on a per-user basis; otherwise, you can mount the share at login. Commented Feb 2, 2018 at 9:45