What's wrong with these Samba settings?

fahrer17 · 4. August 2016

Hi guys,

I know - another thread concerning Samba and permissions...

I have a shared folder for two users ("Ines" and "Rico") where both should be able to write, read and delete files. Unfortunately that doesn't work as intended: "Ines" can't delete "Rico's" files and vice versa.

The settings using the GUI are as shown in picture 1 but in my opinion that doesn't correspond to the rights I see in CLI (picture 2).

I read several days several manuals regarding Unix rights and permissions etc., I don't understand it: Why don't my users have the right to write even if they are allowed to according the GUI settings (as I understand it)??

I'm so confused and don't find my mistake?! Can anybody help me please?

ryecoaaron · 4. August 2016

In the permissions column, the first three columns are for the owner and the next three are for the group. Rico's files are owned by user Rico and group users. The owner has r/w/execute privileges but the group only has read/execute privileges. Since Ines is in the group users but not the owner, that user cannot delete or modify Rico's files. You need to reset the permissions on the files and maybe even change the default creation privileges.

fahrer17 · 4. August 2016

Yeah, I know WHAT's wrong, I just don't understand WHY it is like this. In my opinion all settings are correctly set in the GUI but that doesn't match the result I see when checking it in CLI.

I know I can do a CHMOD on these files/folders but what happens the next time?

How do I permantly change these permissions?

ryecoaaron · 4. August 2016

The default permissions for samba are:
create mask = 0755
force create mode = 0644
directory mask = 0755
force directory mode = 0755

If you don't like these (which you don't), you need to change them. You can override the setting in extra options by adding the lines above with the permissions you want (0775 for dirs and 0664 for files from the sound of it). You will have to fix the existing files though. omv-extras (on OMV 2.x) installs a reset-permissions tab that can fix the existing files for you.

subzero79 · 4. August 2016

There is a switch called enable permission inheritance in the share that should solve that issue. It even has legend saying what is there for.

fahrer17 · 5. August 2016

Ok, I see. So no "real" mistake happened somewhere, it's more an unclear description in the settings I guess.

@subzero79: I know that switch but since I wasn't sure what side effects it's use might cause I left it alone

Thanks for your help guys! I'm sure I can solve my problem now since you showed me where to look at!

fahrer17 · 10. August 2016

So I tested "Resetting Permissions" and it worked in that way that all users can now delete everything.
What I don't like with this solution: Everything is now owned by root (not sure if this might cause any problems later...). So I guess I better CHOWN everything afterwards.

I have checked some older folders+files: I can see my permissions were OK until about April 2016. At one point around then something must have mixed up these permissions

Strange thing: I didn't change or install anything - at least on purpose - since I was absolutely satisfied with my OMV.

subzero79 · 10. August 2016

If you want read only in some users and you're just using samba use the privileges button.

Jetzt mitmachen!