search for: acl_xattrs

On 08/18/2016 08:28 AM, Ralph Böhme wrote: > Hi Eric, > > On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: >> I was testing Samba 4.5rc2 with an existing smb.conf file that I have been >> using since Samba 4.1.x and found that I cannot access data in the share on >> Windows 2012 (my AD server), a Windows 2008 client or on a Ubuntu 16.04 >>

On Thu, Aug 18, 2016 at 12:21:37PM +0300, Uri Simchoni wrote: > On 08/18/2016 08:28 AM, Ralph Böhme wrote: > > Hi Eric, > > > > On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: > >> I was testing Samba 4.5rc2 with an existing smb.conf file that I have been > >> using since Samba 4.1.x and found that I cannot access data in the share on

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

My previous email on this topic get no answer, i try to explain me better. The problem. Simply i was (ab)used, in my previous samba NT-mode domains, to have file created with the group-owner as the UNIX primary group; now, in AD, files get created group-owned by Windows primary group, eg 'Domain Users'. This simply 'breaks' most of my ACLs setup. I've read:

I was testing Samba 4.5rc2 with an existing smb.conf file that I have been using since Samba 4.1.x and found that I cannot access data in the share on Windows 2012 (my AD server), a Windows 2008 client or on a Ubuntu 16.04 client. I built a new version of Samba 4.4.5 using the same procedure as I did for building 4.5rc2 and the 4.4.5 Samba version worked with my smb.conf file. I then created a

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.

Dear list, Setup is: Solaris 11 ZFS + Samba 3.5.10 What is the recommended 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 ?

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

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-samba4.so:

Hi Eric, On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: > I was testing Samba 4.5rc2 with an existing smb.conf file that I have been > using since Samba 4.1.x and found that I cannot access data in the share on > Windows 2012 (my AD server), a Windows 2008 client or on a Ubuntu 16.04 > client. I built a new version of Samba 4.4.5 using the same procedure as I

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

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 sake of simplicity the following permissions apply on

On 2016-08-18 at 12:21 +0300, Uri Simchoni via samba wrote: > On 08/18/2016 08:28 AM, Ralph Böhme wrote: > > Hi Eric, > > > > On Wed, Aug 17, 2016 at 05:56:51PM -0600, Eric Eastman via samba wrote: > >> I was testing Samba 4.5rc2 with an existing smb.conf file that I have been > >> using since Samba 4.1.x and found that I cannot access data in the share on

Hi I am running the "samba-tool domain classicupgrade", and after solving some problems (thread http://lists.samba.org/archive/samba/2013-January/170777.html), now I am getting this error: # samba-tool domain classicupgrade --dbdir ~/sambav3 --realm XXXXXX.YYYYYY.TEST --use-xattrs=yes ~/sambav3/smb.conf -d9 ... init_sam_from_ldap: Entry found for user: XXXXXX init_sam_from_ldap: Entry

Hi folks, No, it does not work. Sorry for the noise. See below. On 31.01.2024 8:51, Peter Milesson via samba wrote: > Hi folks, > > Thanks everybody for your information. > > 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

Problem solved (I hope)! On 31.01.2024 12:40, Ralph Boehme 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

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

Hi everyone, I've recently migrated a file server/domain controller from a Windows 2012 Server to CentOS 7.2 with Samba 4.2.13 running on active directory role mode , everything is working fine except when handling Excel files, when you try to open a file it locks in read-only mode and there is no users accessing the file , anyway you can edit normally if you click on "Notify"

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, >

On 31.01.2024 9:13, Peter Milesson via samba wrote: > Hi folks, > > No, it does not work. Sorry for the noise. See below. > > > On 31.01.2024 8:51, Peter Milesson via samba wrote: >> Hi folks, >> >> Thanks everybody for your information. >> >> I have continued my testing and have got the following to report: >> >> Setting up the share