Question: constructing and setting security descriptor with altered dacl #876
Description
Hello everybody,
first of all thank you for this great library.
I'm trying to implement a file wrapper for this lib that more resembles java.io.File
There are certain operations that I could hardly reflect via standard attributes, like setReadable(), which I would like to use as an example for this discussion.
As, at least theoretically, there is the possibility to set the security descriptor of a file via the DiskShare - but trying to construct or alter one (specifically its DACL) brings me to package private constructors like the one of AceHeader - so my guess is the library does not intend to let the libs user mess with these sort of things.
Am I getting the right intention, i.e. the philosophy being if a user does not have access for a file it should be like this, leaving out loopholes that the user might be able to set permissions which are not yet applied to that file - or am I simply overlooking obvious calls to, e.g. make a certain file readable to the user I'm using to connect to the share in the first place?
Thank you again for the great work.
BR