PépéDansLesOrties
Dabbler
- Joined
- Jun 19, 2021
- Messages
- 24
Hi morganL,
Theoretically, the ACL acts as a hierarchy, isn't it? So if the boss let the manager and the employees access to his data, the employees will indeed be able to access to his data, right?
This way, the ACL of the new dataset includes:
- "root", even if I can't connect with, as the @owner;
- @group & group: klf, my new user primary group;
- user: klf, THE new user with which I should be authorized to connect through samba.
However, despite the theory, I'm that desperate I tested your suggested ACL without "root": I can see FreeNAS on my network but I immediately got the pop-up error message "Windows can't access to...", I can't even see the mounting points.
If I re-modify the ACL as in the screenshots ("root" as @owner, klf as @group, group & user), in both Windows 10 & SparkyLinux:
- I can see FreeNAS in my network;
- I can connect with klf, my new user;
- I can see the mounting points;
BUT I can't access to them:
--> Windows pops up the error message;
--> SparkyLinux pops up again a connection window which expects the good answer from me: neither klf nor "root" seems to be the right one...
Well, not exactly. I'm not trying to remove "root", I'm just trying to connect with a different user since "root" is forbidden...isn't that what you are removing?
Theoretically, the ACL acts as a hierarchy, isn't it? So if the boss let the manager and the employees access to his data, the employees will indeed be able to access to his data, right?
This way, the ACL of the new dataset includes:
- "root", even if I can't connect with, as the @owner;
- @group & group: klf, my new user primary group;
- user: klf, THE new user with which I should be authorized to connect through samba.
However, despite the theory, I'm that desperate I tested your suggested ACL without "root": I can see FreeNAS on my network but I immediately got the pop-up error message "Windows can't access to...", I can't even see the mounting points.
If I re-modify the ACL as in the screenshots ("root" as @owner, klf as @group, group & user), in both Windows 10 & SparkyLinux:
- I can see FreeNAS in my network;
- I can connect with klf, my new user;
- I can see the mounting points;
BUT I can't access to them:
--> Windows pops up the error message;
--> SparkyLinux pops up again a connection window which expects the good answer from me: neither klf nor "root" seems to be the right one...
Last edited: