similar to: ACL set in Windows not set in Samba

>> Side question: How is it even possible that Windows "remembers" the >> ACL it sets but it's not visible on Linux when using getfacl? Windows ACLs are being stored in Extended Attributes using the acl_xattr vfs module. Linux ACLs are not there because the line acl_xattr:ignore system acls = yes is telling Samba not to write them. On 13 May 2018 21:25, Viktor

>> Side question: How is it even possible that Windows "remembers" the >> ACL it sets but it's not visible on Linux when using getfacl? Windows ACLs are being stored in Extended Attributes using the acl_xattr vfs module. Linux ACLs are not there because the line acl_xattr:ignore system acls = yes is telling Samba not to write them. On 13 May 2018 21:25, Viktor

Hi Rowland, Thanks for replying again. On 13 May 2018 at 18:12, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 13 May 2018 17:39:39 +0200 > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > [...] > > > username map = /etc/samba/samba_usermap > > What is in the 'samba_usermap' ? > !root =

On 17.11.2015 18:05, Rowland Penny wrote: > On 17/11/15 16:57, Viktor Trojanovic wrote: >> Hi Mathias, >> >> Thanks for replying. It seems you're describing the situation on the >> AD DC. Computer and user mode access to my DC works fine and without >> any issues but I can't access the shares of my *member* server *in >> computer mode*. In user

Hai Viktor, > > Before posting my share permissions, can you please elaborate what you > mean with "have you removed authenticated users from your share"? I > never had any rights for "authenticated users" on any of my shares. Ah sorry, yes, that was "everybody" ( my error ) keep it > > Maybe I'm setting up shares in the wrong way? >

On 17/11/15 16:57, Viktor Trojanovic wrote: > Hi Mathias, > > Thanks for replying. It seems you're describing the situation on the > AD DC. Computer and user mode access to my DC works fine and without > any issues but I can't access the shares of my *member* server *in > computer mode*. In user mode, it all works just fine. > > Viktor > > On 17.11.2015

Hi Mathias, Thanks for replying. It seems you're describing the situation on the AD DC. Computer and user mode access to my DC works fine and without any issues but I can't access the shares of my *member* server *in computer mode*. In user mode, it all works just fine. Viktor On 17.11.2015 17:19, mathias dufresne wrote: > Here are my (little) view regarding shares accesses. I

Here are my (little) view regarding shares accesses. I write that to clarify things. And it could really be of-topic as Louis seems to have gave solution. There are 2 levels of authorisation for accessing shares: the share level and FS level. For Sysvol I would keep everyone or replace it by "authenticated users" in paranoid mode as the latter refuse non-authenticated users. They are

On 26/05/2019 18:28, Viktor Trojanovic via samba wrote: > Small update: I added "lo" to the interfaces in smb.conf, now smbclient > works also on localhost. But both the other problems remain as described > for now. > > On Sun, 26 May 2019 at 19:17, Viktor Trojanovic <viktor at troja.ch> wrote: > >> I just did a restore of a backed up Samba DC and as feared,

On Sun, 13 May 2018 17:39:39 +0200 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > Setup: Samba AD DC and Samba AD Member Server, Win10 clients only. > Samba version 4.8.1 > > Has something changed recently in the way ACL's are supposed to work? No > My existing shares work just fine but any ALC changes I make using > Windows are ignored in Samba.

On Mon, Aug 22, 2016 at 2:17 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 22 Aug 2016 13:42:08 +0200 > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > > Hi all, > > > > After updating Samba last Friday (from 4.3.3-1 to 4.4.5-1), some > > issues appeared that weren't there before. > > > >

Hi Rowland, On Sun, 26 May 2019 at 19:54, Rowland penny via samba <samba at lists.samba.org> wrote: > On 26/05/2019 18:28, Viktor Trojanovic via samba wrote: > > Small update: I added "lo" to the interfaces in smb.conf, now smbclient > > works also on localhost. But both the other problems remain as described > > for now. > > > > On Sun, 26 May

On Fri, 23 Feb 2024 17:01:58 -0000 miguel medalha via samba <samba at lists.samba.org> wrote: > > > So I've in the global section "vfs objects = recycle acl_xattr" > > (...) > > I hope you removed the line from the share, then. Because if you kept > it, acl_xattr is overridden gain. > > The whole line is overridden, not only some particular vfs

On Sun, 31 Mar 2019 at 14:45, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sun, 31 Mar 2019 14:29:32 +0200 > Viktor Trojanovic <viktor at troja.ch> wrote: > > > On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > On Sun, 31 Mar 2019 13:55:18 +0200 > > >

You're totally right and after i rechecked my conf i've seen that i already set vfs objects = acl_xattr gluster in my share definition. I just played around with these options to see if it helps. Neither combination made any difference so i guess my problem isnt related to the xattr module, it could be related to the gluster module since i did'nt check what would happen if i'd use

> On 04 Jun 2016, at 22:14, Miguel Medalha <medalist at sapo.pt> wrote: > > >> Can someone therefore please explain to me what exactly these GPO >> restrictions are that Samba can't handle? I'd also appreciate if someone >> could list which other GPO I cannot set successfully using RSAT. > > It seems to me that the FAQ is pretty clear. The

Small update: I added "lo" to the interfaces in smb.conf, now smbclient works also on localhost. But both the other problems remain as described for now. On Sun, 26 May 2019 at 19:17, Viktor Trojanovic <viktor at troja.ch> wrote: > I just did a restore of a backed up Samba DC and as feared, I'm running > into issues that have kept me for hours on this already. > >

Setup: Samba AD DC and Samba AD Member Server, Win10 clients only. Samba version 4.8.1 Has something changed recently in the way ACL's are supposed to work? My existing shares work just fine but any ALC changes I make using Windows are ignored in Samba. For example, I'm creating a new folder in Windows inside an existing share and I add user User1 or group Group1 in the security tab.

I missed than one. Very useful hint. Now I can set ACLs again. Thank you. Il 15/02/2018 13:23, Miguel Medalha ha scritto: > Here's what I was looking for. > > On Tue Mar 22 08:19:42 UTC 2016 Uri Simchoni posted the following to > the samba-technical mailing list: > > "Attached patch avoids setting the POSIX ACLs to match the NT ACLs, if > "ignore system

On Sun, 31 Mar 2019 14:29:32 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > > On Sun, 31 Mar 2019 13:55:18 +0200 > > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > > > > On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle