here goes one more revision to my "simple" sharing guide. I've been trying to figure out what determines the default permissions of new files and folders within a CIFS share. Alas, this is far above my paygrade as a lowly server-herder.Ĭrap, now that I have written all this stuff up I don't think the problem was really related to the groups at all. Id like to grant full access for user DocumentsCreator to shares Docs and Meds and read only access to everybody in my network to share Meds. I am assuming that I screwed something up. I haven't had the problem since Thor's Hammer came down on permissions through the zfs aclmode property, but a part of my wonders if this (aclmode=restricted) was just a workaround to problems with the smb.conf parameter "nfs4:mode=special" or how samba handles nfsv4 acls. I have just added and mapped my first dataset (runnning Freenas 9.3). I'm probably contributing my own samba voodoo to the community, but I haven't had coffee yet and I woke up too early. Another helpful reference is Methods For Fine-Tuning Samba Permissions. That means this is all very unscientific. The FreeNAS and Samba (CIFS) permissions and Advanced Samba (CIFS) permissions on FreeNAS videos clarify setting up permissions on SMB shares. It is basically running in standalone/workgroup mode there is no AD/domain controller, and I don't want one if I can avoid it. The server is a FreeNAS system running Samba 4.7.0. Users 1 and 2 have almost feline levels of unreliability in reproducing the results of their samba fuzzing and almost feline levels of indignation when I try to get their fuzzing methods from them (they think I'm mocking their ability to properly use a computer). The problem is that I can't get files on the CIFS share to show correct permissions on the Linux client without forcing vers1.0 in the mount options. The problem didn't seem to appear if the dataset was owned by a user who didn't have an identically-named primary group. Then in typical samba fashion (2+2 = 15), I ended up with random "deny" ACE being generated for the file owner with a few other random ACEs being generated for good measure. I found out that using the Apply Default Permissions option (in FreeNAS) on the share fixes the issue, but when looking at the permissions, I don't really see what is going on "under the hood".# group: evidently, samba got confused by the lack of ACE in the root directory of the share when file ownership changed through user1 generating a new file. The share in question is configured as follows: force directory mode = 0775 When I change the user-ownership of the file to user2 it works fine. I can read the file, delete it, but not overwrite it: share$ cp somefile fileĬp: cannot create regular file ‘file’: Permission deniedĮven though user2 is member of the SomeGroup group that file belongs to. If I right click the file and go to properties and then security, it shows that the only person who can make changes is the: root(Unix user\root). I'm running FreeNAS and using the windows permissions settings (not Unix). Now, when I mount the share on which this file resides using CIFS through fstab: //nas/share /path/to/share cifs username=user2,password=****,uid=user2,gid=user2 0 0 I'm trying to change some permissions on a folder. This how-to assumes that you have the FreeNAS server set up properly and that you have mounted your various drives’ and set up the directories you need. On the NAS there is a file as follows: -rwxrwxr-x+ 1 user1 SomeGroup 8820 Nov 27 15:59 file* Creating permissions & users on FreeNAS By Richard Novem2 Comments Here is a good way to set up users and groups with permissions on FreeNAS. I have a smbd 4.1.9 on FreeNAS 9.2.1.6 and having some permissions troubles.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |