[Samba] Inconsistent SYSVOL ACLs

[Rowland Penny]

On 03/04/2023 12:02, Michael Tokarev via samba wrote:
> 03.04.2023 02:53, Anderson Sampaio Mello via samba пишет:
>> First of all thank you all for the answers and for trying to help me.
>>
>> I agree with you michael regarding the parameters passed in the 
>> ./configure
>> command, the location is not part of the problem.
>>
>> The file system used is XFS. and the strace command logs are in the
>> attached link
>> https://drive.google.com/file/d/1R_b6TzeJVmNIpnlkPfRk0CtkpeU4dgcg/view?usp=share_link
> 
>  From this trace:
> 
> getxattr("/usr/local/samba/var/lib/samba/sysvol/exemple.com", 
> "security.NTACL", NULL, 0) = 320
> getxattr("/usr/local/samba/var/lib/samba/sysvol/exemple.com", 
> "security.NTACL", 
> "\4\0\4\0\0\0\2\0\4\0\2\0\1\0\35\26\34P,\223\25\234{\21\3324g-\34\rgD"..., 320) = 320
> getxattr("/usr/local/samba/var/lib/samba/sysvol/exemple.com/scripts", 
> "security.NTACL", NULL, 0) = 0
> getxattr("/usr/local/samba/var/lib/samba/sysvol/exemple.com/scripts", 
> "security.NTACL", "", 0) = 0
> write(2, "ERROR(runtime): uncaught excepti"..., 63ERROR(runtime): 
> uncaught exception - (11, 'Buffer Size Error')
> 
> So it looks like we have a bug in the python code. 

Possibly, but strange it has taken over 10 years to show up.
There is also the fact that 'getxattr' is a kernel call and if the '63' 
is relevant, then there is something wrong with 'security.NTACL' 
sizewise (which could be that it doesn't exist)

> After successful 
> getxattr() call
> (for a fun filename - exemple.com) it return an error. 

'exemple.com' will be his dns domain.

> It smells like 
> the code
> does not expect to see 0-length NTACL.

Which begs the question, why is it '0' length, has the OP done something 
he hasn't told us ?

Rowland