Worry about rights on SMB shares.

[Totor]

Hello everyone.

I'm a new unraid user and would like your help in accessing/modifying my shares.

 

I've set up various shares into which I've transferred files from my old NAS using rsync.
I then created a user to use my shares in SMB on Windows 11 and MacOS. 
I set the shares to SMB "Private" and gave my user read/write rights. They mount on my Windows and Mac without a hitch.

However, it's impossible to modify or drop anything in my shares.

 

The only way I've found is to make my user the owner of the files on the command line.
New problem: my unraid can no longer manage these files... Rights problem!

 

I could change them to 777, but that would mean I'd have to do it by hand, and that's not very secure.

I'm going round in circles and that's why I'm asking for your help.

 

If you have a solution, I'd love to hear from you!

untotor-diagnostics-20230929-1023.zip

Edited September 29, 2023 by totor

[itimpi]

You should probably run Tools->New Permissions (probably better named as Reset Permissions) on the shares to get them to the Unraid defaults so that the SMB level ones then get applied for network access.

[Totor]

Thank you very much, that was the solution ! 👌

It's true that if this button was better named I would have tried it 😁

Last question: does this mean I have to do this every time I add a new user or change their rights on a share?

[itimpi]

3 minutes ago, Totor said:

Last question: does this mean I have to do this every time I add a new user or change their rights on a share?

Should not need to do this if files are copied over the network.   It tends to be needed when some other mechanism (e.g. rsync) is used to copy the files that bypasses setting the security the way it would be if done via SMB.   There should never be any problems with rerunning this utility though if needed.

[Totor]

Ok now I understand the origin of my worries then.
I transferred all my files from my NAS to unrraid with rsync.

 

Thanks again for your help.

[Totor]

I tested with the Filebot docker and had the same problem again.
Ability to view and read files but not to modify them.

To solve the problem I passed the "umask=011" directive to the docker and now everything works perfectly.

If this is of any use to anyone.