in reply to Re: Win32API::Registry::RegGetKeySecurity how to unpack the structure of $pSecDesc?
in thread Win32API::Registry::RegGetKeySecurity how to unpack the structure of $pSecDesc?
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:
use Win32::TieRegistry( Delimiter => "/" ); my $sec; $Registry->{"LMachine/Software/7-Zip/"}->RegGetKeySecurity( 4, $sec, [ +] );
(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
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Win32API::Registry::RegGetKeySecurity how to unpack the structure of $pSecDesc? (misc)
by Sioln (Sexton) on Jan 16, 2006 at 07:11 UTC | |
by tye (Sage) on Jan 16, 2006 at 07:16 UTC |