Bug 33163 – samba-tool ntacl does not work on Samba/NT systems

Bug 33163 - samba-tool ntacl does not work on Samba/NT systems


Summary:	samba-tool ntacl does not work on Samba/NT systems

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba
Version:	UCS 3.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-06 18:10 CET by Arvid Requate
Modified:	2017-04-24 18:03 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
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 Arvid Requate

2013-11-06 18:10:03 CET

Currently the samba-tool command does not work on Samba/NT systems, due to missing libraries. This is a problem of the current debian package, as some of the missing shared libs are in libdcerpc-server0 or worse in samba-ad-dc and some of the python libs seem to be missing too.

Since ntacls are also active by default on Samba/NT systems, it would be useful for debugging and administrative proposes to be able to do:

samba-tool ntacl get --as-sddl /opt/share1sl/Foo1.txt

In future versions of the samba package we should check if pacakging can be improved to make this possible.

Comment 1 Arvid Requate

2017-04-24 18:03:05 CEST

This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

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