commented ntsecdesc type conversion so ACEs return.
I stayed up all night playing a CTF and all I found was a hash.
Hi skelsec, I made a pull request. Why did the enc dictionary of translations contain nTSecurityDescriptor and print out bad bytes? By commenting it out of there so the conversion fell through to the lookup table in the elif, the ACEs were loaded instead which is more useful information.
I like msldap because it works well which is what got me pulling on this thread.
Hello, thank you for the PR!
May I ask what bad bytes are you referring to?
This PR will be rejected, because the nTSecurityDescriptor must be returning bytes or bytearray object, for two reasons:
- this would impact the API in a major way.
- Parsing
nTSecurityDescriptorto an object takes a lof of resources, and some queroies could easily return hunderds ofnTSecurityDescriptors which would slow down the app considerably
No bad bytes. I misinterpreted them. I like the objects. I'll see if I can get my script to handle the bytes else use my fork which uses code you had already written but didn't appear to be using.