Bug 37624 – reset well known ACL after takeover

Bug 37624 - reset well known ACL after takeover


Summary:	reset well known ACL after takeover

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Takeover
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:	50635
	Show dependency tree / graph

Reported:	2015-01-27 02:16 CET by Kevin Dominik Korte
Modified:	2019-12-12 22:05 CET (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Kevin Dominik Korte

2015-01-27 02:16:04 CET

Samba 4 doesn't currently honor all variants of ACLs for LDAP objects that AD supports and one can't set them using the samba-tools or AD Tools. However the AD-takeover copies unsupported ACLs over from the Windows DC. In most cases these are then ignored, however if there are ACLs set on well known containers, Samba might not work correctly.

To fix it one can simply call 
samba-tool dbcheck --yes --fix --reset-well-known-acls

it might make sense to test the output of "samba-tool dbcheck" for the string "nTSecurityDescriptor" and call the above command if the error was detected.

Comment 1 Arvid Requate

2015-01-27 11:07:58 CET

Can you provide an example or log?

Comment 2 Arvid Requate

2015-02-16 14:57:35 CET

I propose to simply add the switch "--reset-well-known-acls".

Comment 3 Stefan Gohmann

2019-01-03 07:18:22 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.