|
|
| Keep It Simple, Stupid | |
| PerlMonks |
Re^2: Win32API::Registry::RegGetKeySecurity how to unpack the structure of $pSecDesc? (misc)by tye (Sage) |
| on Jan 13, 2006 at 12:31 UTC ( [id://523038]=note: print w/replies, xml ) | Need Help?? |
This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.
Unfortunately, no one has written (well, released, AFAIK) Win32API::Security and the modules I've seen that deal with security don't take the general approach I pushed for with Win32API::* so they don't handle security descriptors directly. For example, some only work on files. I /have/ found Reg[GS]etKeySecurity() useful in cases, even so. I'd use the GUI to set the desired permissions on a reference key and then just copy those permissions to other keys (such a new keys) via my script. I'd also use Win32::TieRegistry:
(Not recommending using "4" over importing the correct definitions from Win32, just being cheap and short for the sake of emphasizing the other aspects of the example.) - tye
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||||||||||