| ▲ | mmh0000 3 hours ago | ||||||||||||||||
Sure, if you (the admin) have full control over the NFS server, the network, and the client devices, NFS can be secure with the help of Kerberos. But this isn't a simple thing. A Kerberos server needs to be set up, Kerberos clients need to be configured on the NFS server and client, tickets need to be issued, firewall ports need to be opened, and user accounts need to be centrally managed. That's all fine for an Enterprise. Now, how about this common scenario: I want to run a file-sharing server on my network. I want a random "friend" to come over and grab a copy of a file, but I don't want them to see any other files on the NFS server. So, the "friend" has root access on their device. They can just log in and lie to the NFS server, claim they're my UID, and see all my files that I didn't want them to access. Configuring KRB in that scenario is totally impractical. | |||||||||||||||||
| ▲ | skydhash 2 hours ago | parent [-] | ||||||||||||||||
> Now, how about this common scenario: I want to run a file-sharing server on my network. I want a random "friend" to come over and grab a copy of a file, but I don't want them to see any other files on the NFS server. How is that a common scenario? Why not give them your drive and the encryption key while you’re at it? It would be way faster. The correct scenario would be to just copy the file and serve it with ftp or http on another interface. | |||||||||||||||||
| |||||||||||||||||