SMB Share Permissions with extra user

[sasbro97]

I'm new to Unraid and a bit confused about the permissions for files. I created a separate user just for SMB access on my PC. I gave him Read/Write rights for a user share.

My files in this folder have different permissions. I don't know. Happend after migration from another server.

 

Its only important that the other permission is set to Read/Write. Otherwise it won't work. But why? I thought I got a user for that. Okay it's not the owner but why does it not belong to the group? Seems strange to me.

Edited May 20, 2023 by sasbro97

[MrGrey]

SMB can be strange (it's a Microsoft product). What is your end goal?... Sharing what with who?

 

You show sharing your "appdata" folder and that's not a great idea unless your someones kid hacking Daddy's (edit: or Mommy's) Unraid server.

 

MrGrey.

Edited May 20, 2023 by MrGrey
Political correctness

[sasbro97]

You are not answering my question. I am not a kid and just want to edit my files on my Windows PC. I always did it like this. For example a dashboard.

 

Can you now tell me what is going on technically and answer my question?

[itimpi]

The permissions on the appdata folder are determined by the Docker Containers and not by Unraid itself so it is not a good example to use for typical Unraid permissions.   Changing these permissions can have adverse affects on the containers.  The permissions containers set may also preclude the files being editable at the SMB level.  

 

If you have the Dynamix File Manager plugin installed then it can edit text files anywhere within the Unraid file system including within the appdata share.

[sasbro97]

@itimpi okay we take another example. Can you just tell me if I'm right or wrong?

 

It is always mandatory to set the other permission to Read/Write if I want Read/Write access on a private/secure SMB, right? And in addition the user needs the same permissions, right?

[Frank1940]

"appdata", as a 'Share' is a special animal that stores information about Docker applications.  I have never heard of a reason that anyone has to be able to access it via SMB.  In fact, unless you have a very special reason for doing so, you are best served by not doing so.  If there should be a Docker app that does allow user access to information stored in appdata via SMB, it should have already setup the proper permissions in its portion of the 'appdata' file structure.  

 

The only shares that you should ever share via SMB are the ones listed by this command:

ls -al /mnt/user0

 

Messing around with the permissions in 'appdata' may break some Dockers!  I imagine that is the reason why many Dockers have set their permissions as they are for their 'data' in 'appdata' is to prevent exactly what you are trying to do.  As @itimpi pointed out the Dynamix File Manager will allow you edit the text files in 'appdata' because when you use that plugin, you become the superuser, root,  and that user is permitted to do anything he/she wants.   (Linux/UNIX has the design philosophy that all users have only enough permission to do things on the system that is needed to do their work.  If they want to do anything else (other than that work), they will be denied permission to do so.

 

One thing that Unraid does is to prevent root from being a SMB user.  See this line in  /etc/samba/smb/conf:

 invalid users = root