in reply to Windows Security

Personally, I shell out to icacls.exe.

It will for the most part prevent you from screwing things up too badly, whereas using the APIs -- assuming you can find an up-to-date and maintained module that gives you access to them -- it is extremely easy to screw things up completely.

I don't trust myself to program an api that complex; should I trust someone else?


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I'm with torvalds on this
In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

Replies are listed 'Best First'.
Re^2: Windows Security
by Anonymous Monk on Feb 06, 2015 at 04:58 UTC

      The most significant information there are the dates: March 2004.

      icacls (the replacement for the notoriously inept cacls) first came with Vista which shipped in 2006/2007. With an API that complex, and that has gone through many changes, I'd be very reluctant to use a third party tool that is 10 years out of date.


      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority". I'm with torvalds on this
      In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked