search for: acl_xattr

...ity = ads >> realm = ERIC.LOCAL >> workgroup = ERIC >> netbios name = C1-GW03-T5 >> idmap uid = 500-10000000 >> idmap gid = 500-10000000 >> winbind use default domain = Yes >> winbind nested groups = Yes >> map acl inherit = yes >> vfs objects = acl_xattr streams_xattr >> acl_xattr:ignore system acls = yes >> load printers = no >> printcap name = /dev/null >> >> [zzz] >> path = /zzz >> writeable = yes >> browseable = yes >> >> >> The line causing the problem with 4.5rc2 is: >>...

...t; >> workgroup = ERIC > >> netbios name = C1-GW03-T5 > >> idmap uid = 500-10000000 > >> idmap gid = 500-10000000 > >> winbind use default domain = Yes > >> winbind nested groups = Yes > >> map acl inherit = yes > >> vfs objects = acl_xattr streams_xattr > >> acl_xattr:ignore system acls = yes > >> load printers = no > >> printcap name = /dev/null > >> > >> [zzz] > >> path = /zzz > >> writeable = yes > >> browseable = yes > >> > >> > >>...

Hello all, we want to change the configuration of our Samba domain member file servers to use unix_primary_group=yes After some experiments I was able to get it to work, but only with vfs objects = acl_xattr commented out. With acl_xattr enabled the primary group is still displayed correctly in the output of smbstatus, but new files are not created with with this primary group. The created files have the default group 'users' instead. Is it a? bug in the acl_xattr module? I used the lat...

...dows ACL) but still there's some 'gray zone' where things are different. For example, in my main share i have (directly caming from NT setup): [Media] comment = Contenuti Multimediali map acl inherit = Yes path = /srv/media read only = No store dos attributes = Yes vfs objects = acl_xattr volume = Media so my setup seems a 'Windows ACL', but still i have 'CREATOR OWNER' and 'CREATOR GROUP'. Second, in intimacy with the first, seems to me that the real differences between 'POSIX' and 'Windows' ACL is not only 'acl_xattr' module, but...

...line that caused the problem. Here is my cut down smb.conf file: [global] security = ads realm = ERIC.LOCAL workgroup = ERIC netbios name = C1-GW03-T5 idmap uid = 500-10000000 idmap gid = 500-10000000 winbind use default domain = Yes winbind nested groups = Yes map acl inherit = yes vfs objects = acl_xattr streams_xattr acl_xattr:ignore system acls = yes load printers = no printcap name = /dev/null [zzz] path = /zzz writeable = yes browseable = yes The line causing the problem with 4.5rc2 is: acl_xattr:ignore system acls = yes For my tests the /zzz directory was created clean each time before s...

On 08. aug. 2018 22:30, Dante Colo wrote: > > If you add to vfs module to a share you also have to explicit add acl_xattr , that's what i do when i want to add another module and keep acl_xattr on the same share, if i'm not doing right way someone correct me . > I am already have 'vfs objects = zfsacl' set for my ZFS shares so acl_xattr does not help at all. acl_xattr adds two more entries to t...

...ommended way nowadays of performing strict permissions mapping between Samba and Windows NT 6.1 ? And a more broader question: is it desirable ? As we know ZFS has native NFSv4 ACL's and this would mean that permissions applied on Windows side should have an exact match on the ZFS side. Is it acl_xattr module still needed ? Example: [samba] path=/export/home/samba writable=yes vfs objects=acl_xattr By the way: acl_xattr is production ready now if I am not mistaken ? Dragos

Does you filesystem support extended attributes? What does "|getfattr -n security.NTACL |filename" return?|| On 30.01.2024 16:13, Peter Milesson wrote: > Hi folks, > > It seems that the setting acl_xattr:ignore system acls = yes reduces > Windows compatibility when defined for a share. In all attempts I have > used Windows tools (except editing smb.conf) > > Assume there is a share, where the files and folders in the share root > should at least be readable by anybody having access t...

dear list, we have a little problem with our samba server. it fails to load acl_xattr.so out of nothing and affects new connections as they cannot be established. samba throws: [2016/03/08 15:41:25.973874, 0] ../lib/util/modules.c:48(load_module) Error loading module '/usr/lib/x86_64-linux-gnu/samba/vfs/acl_xattr.so': /usr/lib/x86_64-linux-gnu/samba/libsmbregistry-sa...

...file: > > [global] > security = ads > realm = ERIC.LOCAL > workgroup = ERIC > netbios name = C1-GW03-T5 > idmap uid = 500-10000000 > idmap gid = 500-10000000 > winbind use default domain = Yes > winbind nested groups = Yes > map acl inherit = yes > vfs objects = acl_xattr streams_xattr > acl_xattr:ignore system acls = yes > load printers = no > printcap name = /dev/null > > [zzz] > path = /zzz > writeable = yes > browseable = yes > > > The line causing the problem with 4.5rc2 is: > acl_xattr:ignore system acls = yes this cha...

Dear all We run Samba 3.5.8 on a Solaris 11 box on top of ZFS We got the impression that the VFS module acl_xattr provides the best way of keeping Windows ACLs. We don't have concurrent NFS or local users so it's Windows only. The clients as well as the Samba server are members of an AD domain. Creating files/directories works as expected and also manipulating permissions for the initial user/group do...

Hi folks, It seems that the setting acl_xattr:ignore system acls = yes reduces Windows compatibility when defined for a share. In all attempts I have used Windows tools (except editing smb.conf) Assume there is a share, where the files and folders in the share root should at least be readable by anybody having access to the share. For the...

...t; >> workgroup = ERIC > >> netbios name = C1-GW03-T5 > >> idmap uid = 500-10000000 > >> idmap gid = 500-10000000 > >> winbind use default domain = Yes > >> winbind nested groups = Yes > >> map acl inherit = yes > >> vfs objects = acl_xattr streams_xattr > >> acl_xattr:ignore system acls = yes > >> load printers = no > >> printcap name = /dev/null > >> > >> [zzz] > >> path = /zzz > >> writeable = yes > >> browseable = yes > >> > >> > >>...

...ckend 'posixacl' Successfully added vfs backend '/[Default VFS]/' Successfully added vfs backend 'dfs_samba4' Initialising custom vfs hooks from [/[Default VFS]/] Successfully loaded vfs module [/[Default VFS]/] with the new modules system Initialising custom vfs hooks from [acl_xattr] vfs module [acl_xattr] not loaded - trying to load... Loading module 'acl_xattr' Loading module 'acl_xattr': Trying to load from /usr/local/samba/lib/vfs/acl_xattr.so Module 'acl_xattr' loaded Successfully added vfs backend 'acl_xattr' Successfully loaded vfs module...

...t; > I have continued my testing and have got the following to report: > > Setting up the share with either root:"Domain Admins", or > "Administrator":"Domain Admins" as owner, while setting permissions on > the share folder to 0777 from the start, and acl_xattr:ignore system > acls = yes on the share definition in smb.conf (I did not forget to > restart smbd and winbind) > > Then in Windows Computer management/Security I get the following list: > Owner: (root or Administrator) > > ?? root (or Administrator)??? Full Control??? This f...

...oehme via samba wrote: > On 1/31/24 12:02, Rowland Penny via samba wrote: >> Which looks correct to myself, so a bug ? > something to look into in more detail, ie logs and network traces. :) > > -slow Hi folks, I added the following parameter to the share definition in smb.conf: acl_xattr:default acl style = windows Now the share definition is: [Migrtest] ??????? path = /data/migrtest ??????? read only = no ??????? acl_xattr:ignore system acls = yes ??????? acl_xattr:default acl style = windows What I do now is the following: * Create the folder for the share * Set owne...

On Wed, 31 Jan 2024 11:53:44 +0100 Ralph Boehme <slow at samba.org> wrote: > On 1/31/24 11:19, Rowland Penny via samba wrote: > > When I logged into Windows and connected to a share that has > > 'acl_xattr:ignore system acls = yes' set and right clicked on its > > icon in Explorer and selected 'Properties', I found that 'EVERYONE' > > was listed. I removed 'EVERYONE', clicked 'Apply' then 'OK', which > > completed without error. 'EVERY...

...I debug class = yes debug prefix timestamp = yes strict locking = no oplocks = no level2 oplocks = no [netlogon] path = /var/lib/samba/sysvol/am.local/scripts read only = no browsable = no [sysvol] path = /var/lib/samba/sysvol read only = no browsable = no [Homedirs] vfs objects = acl_xattr store dos attributes = yes map acl inherit = yes browsable = no writable = yes path = /data/samba/homedirs [Juridico] vfs objects = full_audit,acl_xattr acl_xattr:ignore system acls = yes full_audit:prefix = "%I|%u|%P" full_audit:success = rmdir rename unlink full_audit:failur...

yes i have, this is my share-config: [share] path = /mnt/gluster/daten/share/ public = yes writeable = yes browseable = yes inherit permissions = Yes inherit acls = Yes map acl inherit = Yes nt acl support = yes vfs objects = acl_xattr F?bio Leandro Rodrigues Cordeiro schrieb: > Hi, > > Have you tried adding the share writeable? > [share] > writeable = yes > > att, > F?bio Cordeiro > PUC Minas > www.taichous.com > > -----Mensagem original----- > De: Wolfgang [mailto:listener at may.co.at]...

...ontinued my testing and have got the following to report: >> >> Setting up the share with either root:"Domain Admins", or >> "Administrator":"Domain Admins" as owner, while setting permissions >> on the share folder to 0777 from the start, and acl_xattr:ignore >> system acls = yes on the share definition in smb.conf (I did not >> forget to restart smbd and winbind) >> >> Then in Windows Computer management/Security I get the following list: >> Owner: (root or Administrator) >> >> ?? root (or Administrato...