windowvast.blogg.se - Freenas cifs permissions

#Freenas cifs permissions how to
#Freenas cifs permissions iso
#Freenas cifs permissions windows

#Freenas cifs permissions iso

The latest ISO I had was, so went with that. In frustration I reinstalled FreeNAS from scratch.

#Freenas cifs permissions windows

I don't care about access rights, so tried just about everything: switching to Windows permissions, setting those via a Windows client (access denied), reseating the "sane" defaults via setfacl (as per a 9.2-era bug report), "nt acl support = no" on the particular share etc. Copying a new file worked OK, but once in place it would only read or delete. I can't pinpoint when it happened, but in the end I was on FreeNAS-9.3-STABLE-201505130355. My 4+ year old ZFS share (unix permission type, open-ended guest account RW access via CIFS) stopped allowing modification of existing files. Ugly hack, however, I did just commit the fix that does the right thing. Service ix-pre-samba start # create config (and group mapping) with known SID Net groupmap delete # this should blow away all mappings The newly created group mappings at this point had a consistent SID, however, it was not THE SID that was now correct -) So, to fix that: The "fix" was brute force, as follows:Īt this point, is where the bug occurs. So, when I looked at your group mappings, you had several different SID values. Once the group mappings were introduced, it mattered. We originally didn't even have group mappings, so this didn't matter. So every time FreeNAS would get rebooted, a new SID was generated. I do not recall the exact version, but I want to say it was 9.2.1.8. Also, there was a point when the samba SID didn't used to get saved.

The issue was with the samba group mappings happening before the samba SID was being saved.

#Freenas cifs permissions how to

I have no idea how to do that and basically, that's what I need to do. "getfacl" will also give me the correct group name, and not that unknown account crap.īUT what if I want to add ANOTHER group and then set specific permissions for that one. If I keep that "unknown account" thing, and I modify the permissions, then if I go in the shell and do a "getfacl" I will be able to confirm my modification worked and now the group had correct permissions. Like I said there's ME and an unknown account with bunch of random characters between parenthesis, which I guess is the group. In the initial screen (in properties > security) So I'm stuck with being only able to give permissions to users, and not groups, which really doesn't do the trick for me.

And an object called "Unknown account" with a bunch of characters between parenthesis, which I guess is the groupįirst I remove everyone I don't even want to give out read privilege to everyone, but I've tried without doing that it doesn't matter.īut the only "objects" I can find are the usernames, when I launch a search.

I go right click on the share, and go to the security tab. I see the share, I can access it, then I want to tweak the permissions.įrom what I've read on the forum, the preferred way to mess around with permissions is through the WINDOWS GUI and not shell (setfacl, etc.) or FreeNAS GUI (don't mind the auxiliary parameters, even if I remove them, it doesn't matter) Then I created a CIFS share with apply default permissions.įinally configure CIFS service with those options: The conclusion was that it should be fixed in 9.3 so I let that aside.īut now running 9.3 it still doesn't work.įor this dataset I set the permissions, in FreeNAS GUI to : I started a thread sometimes during last year on that same issue but I can't seem to find it.