[SMB] Share permissions not working as expected

[diglam]

Hi,

I shared "top_folder" with below group permissions and "Same permissions for all subdirectories" option was checked.

pusers -> Read/Write
family -> Read

* Members of "family" group can enter "top_folder" share and can not create folder or write there as expected.

* But If a member from "pusers" group create a folder (for example "sub_folder") in "top_folder", members of "family" group also have write permission inside "sub_folder", they can create folder or write there. Normally I expect only read permission like parent folder.

[TMSupport]

Please choose the option "Replace permissions on all subdirectories with permissions of this folder".

1601945762(1) (1).jpg

[diglam]

Please choose the option "Replace permissions on all subdirectories with permissions of this folder".
1601945762(1) (1).jpg

Not worked

[diglam]

TMSupport

Were you able to reproduce same situation/error?

[diglam]

Please choose the option "Replace permissions on all subdirectories with permissions of this folder".
1601945762(1) (1).jpg

Hi @TMSupport
I still need help. Is this a bug or I'm doing something wrong?

[TMSupport]

Hi, may I know the folders name and your current TOS version? Could you give more specific example in return？

[diglam]

Names are not important. I tested just now on a newly formated/reinstalled TM F2-421 as below:
1- Create a user named as "user_rw"
2- Create a user named as "user_ro"
3- Create a user group named as "group_rw" and add "user_rw" to this group
4- Create a user group named as "group_ro" and add "user_ro" to this group
5- Create a new share "test", give "Read/Write" permission to "group_rw" and give "Read only" permission to "group_ro"
6- Try to create a folder in shared folder "test" with "user_ro" on a client PC, you won't be able to create folder as expected, it is OK
7- Create a folder named "New folder" (name not important) in shared folder "test" with "user_rw" on a client PC
8- Try to create a folder inside "New folder" created on previous step with "user_ro" on a client PC, you will be able to create now, not expected because "user_ro" has "Read only" permission, NOT OK!!

As I said before, names are not important, you can use whatever you want.

Model: F2-421
TOS version: 4.1.30-2008051459

[TMSupport]

Actually the folder name is important, the permission to sub folders which have space and some special characters will not be configured and remembered successfully.
Please change the sub folders name "new folder" to "newfolder" and test the permission again.

[diglam]

Actually the folder name is important, the permission to sub folders which have space and some special characters will not be configured and remembered successfully.
Please change the sub folders name "new folder" to "newfolder" and test the permission again.

I tried with name "newfolder" but result is same, "Read only" can write in newly created folder.

[diglam]

May ask to other users to test this situation please?

I think this is a big permission bug if I'm not doing something wrong.