The Samba-Bugzilla – Bug 6401
Modification of nTSecurityDescriptor attribute removes owner and group
Last modified: 2009-11-26 04:48:33 UTC
After enabling "Advanced Features" within ADUC, you can modify the permissions on an object using the Security tab under the object's Properties. After modification of an object's security permissions, the object no longer has entries for the owner or group in the SDDL.
After creating an OU named "Test", the nTSecurityDescriptor atrtibute SDDL (via ldbedit) is:
After granting Read privileges to Backup Operators on OU Test, the nTSecurityDescriptor atrtibute SDDL (via ldbedit) is now:
Notice how the new SDDL contains DACL ACE's, but no owner or group. Looking at the Owner tab in the Advanced security settings for Test shows "Unable to display current owner." as the current owner.
Created attachment 4198 [details]
Capture of modify operation
The attached capture shows the modify request in frame 414. Note that there is no data for owner SID, group SID, or SACL (no offsets to any of those contained in the NT Security Descriptor).
After looking into this some more, it appears that security descriptor LDAP operations (add, modify, search) are controlled by an SD flags control (LDAP_SERVER_SD_FLAGS_OID).
See the following for details:
In frame 414 of the previously attached capture, the last 4 bits of the LDAP_SERVER_SD_FLAGS_OID controlValue (4) indicate that the modify request specifies the modify is for the DACL of the SD.
Andrew Kroeger: did you consider to write a patch?
Did the new LDB module (descriptor) change something here or solved the problem?
I don't know for andrew K, but for me it's the case even with a freshly provisioned samba !
I also claim that the problem still persists (a quick test shows it). Hopefully someone skilled (like Nadezhda) wants to take this and write a fix.
Are we any further here?
Descriptor creation does not work on modify. I am working on this at the moment, should be fixed soon.
I have added support for sd_flags control and fixed some major bugs on modify, so there is a very good chance this is fixed. Could someone try? I am not sure how to reproduce it.
Retested - it's fixed. Thank you very much, Nadya!