October 19, 201411 yr I'd like to exclusively use NFS but I need some sort of security, preferably with a password. I'm not exactly sure how to implement this with NFS. If not possible, can I export the share to only a single IP address. Would I need to append something in the go file to accomplish this? Guesst I would need something that removes the '*' in the exports file and replaces it with an IP address? As I would only allow one IP access to the shares. Is there a cleaner way to do this?
October 20, 201411 yr First, you need to running either the Plus or Pro version (5.0.6 preferably). Second, have you read and implemented security as outlined here: http://lime-technology.com/wiki/index.php/UnRAID_Manual_5#User_level_security_2
October 21, 201411 yr Author Thanks for the reply. But how would one implement Private NFS security on the client side if mounting the share via autofs. What does the rule mean for Private NFS?
October 21, 201411 yr Thanks for the reply. B But how would one implement Private NFS security on the client side if mounting the share via autofs. What does the rule mean for Private NFS? I had only limited experience with UNIX/Linux several years ago and my knowledge was very limited in the area of security as I was never involved with computers with wide accessibility where security was a real issue. For the client side implementation, you are going to have to dig into the documentation for your variety of Linux to find the answer to your question. As far as what is happening on the unRAID share side, I believe that (in reality) all of the security for both NFS and SMB is really done in the underlining Linux file system so what happens with the various security settings for shares applies equally for both NFS and SMB.
Archived
This topic is now archived and is closed to further replies.