Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I want to enable file sharing between servers and clients, both linux. I don't want to rely on machine trust like in NFSv4 because client users will have root privileges. What are my options besides SMB (SAMBA)? Does OpenAFS support user level authentication & access? Using mounted WebDAV/ftp/sshfs seems silly for LAN.

share|improve this question
    
Do you mean they have root access to the servers or just their own client machines? –  wag2639 Jun 23 '10 at 5:37

5 Answers 5

I am not sure I fully understand:

"I don't want to rely on machine trust like in NFSv4 because client users will have root privileges."

If you mean the client users will have root privileges on the client and you don't want them to have root on the host then you just don't use the "no_root_squash" option. You can also do things like disabling setuid to help reduce the risk to the client from the server as well.

You also have the option to use kerberos with NFSv4, see this link.

So in other words, NFSv4 might give you the security you need while being a little bit more ... (scalable?) .. the using sshfs everywhere. It still might not be what you want, but I wouldn't give up on it too soon.

share|improve this answer
    
For example, I have two projects /joeisworking and /mattisworking. Even if I do squash root, matt from his workstation can access joe's. –  Konrads Jun 16 '10 at 13:50
2  
@Konrads: Not if you use kerberos, as Mr. Brandt mentioned. Even if matt has root on his own workstation, he cannot get Joe's TGT. –  janneb Jun 16 '10 at 18:36
    
I'm thinking Konrads just isn't sure how to configure NFS, or has experienced a poorly configured network previously. NFS can be very secure, and can accomplish exactly what is described in the question. I would argue that NFSv4 is one of (if not the most) secure network file system (when properly configured). –  Chris S Jun 17 '10 at 18:57

With Kerberos, only the kdc server grants authentication tokens. A client machine by itself can only authenticate as a host (and that is if you give it the keytab to a matching nfs/client-hostname@REALM principal), and that only gives it the right to talk to the nfs server. It's the users who have the ability to authenticate, and the nfs server only authorizes them to access their own files. With sec=krb5p the server prevents snooping and alteration as well.

Being root won't give your users inappropriate privileges. The only way they'd get access to more files is by hacking each other's machines, hacking the nfs server or the kdc. NFSv4 with Kerberos fits your security requirements well.

Here is more on the security model:

If you're looking at a deployment, here are some debian/ubuntu centric tutorials. I picked simple setups without LDAP. These distributions have debconf-based configuration that gets you some of the way there.

My additions: you don't need to specify a des-cbc-crc enctype, but you need to allow_weak_crypto in krb5.conf so that the communication protocol can use des-cbc-crc for stream encryption. This will become unnecessary in 2.6.35 kernels.

If you're looking at something appliance-like, there is FreeIPA.

share|improve this answer
    
This is interesting, so far I understood that there is only server to server authentication in NFSv4 and then the system that mounts the exported volume is responsible for sorting out the permissions (squash_root_fs being the exception). Can you provide some links to docs? –  Konrads Jun 17 '10 at 7:22

sshfs is the way to go. On the client:

sshfs -o idmap=user,workaround=rename user@server:/home/user/share /home/user/share

Permissions same as ssh... because you are using ssh! Nice thing is you don't have to touch anything on the server, assuming sshd is installed and running properly. Might not have the performance as the other suggestions, but it is very simple.

share|improve this answer

samba does actually sound like your best bet. samba does have unix extensions so when mounted using as cifs on linux it should show proper unix permissions and whatnot. I think that is going to be the best option for your constraints. if that doesn't work out sshfs could be used in a pinch but it won't have as good performance or integration into the OS as samba.

share|improve this answer

Does OpenAFS support user level authentication & access?

Yes, it sounds like OpenAFS would satisfy your requirements here, but so would Kerberized NFSv4. In both of those environments, you do not need to "trust" clients; access control is enforced by servers. Previous versions of NFS did require you to effectively "trust" clients, but Kerberized NFSv4 does not. OpenAFS has never required "trusted" clients, and also relies on Kerberos for authentication and security.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.