in reply to Changing registry permissions

“Security on Windows” is something that you possibly should not assume that a program can do at all.   (As the Windows community oh-so-slowly begins to figure out that it needs to use Windows’ many security features, it tends to over-react.)   In most cases that I have seen, when a program requires this-or-that registry changes to be done, particularly when those changes concern permissions on things, those changes are usually done by an installer, not by the program itself.   Maybe you should consider using a similar approach.

Replies are listed 'Best First'.
Re^2: Changing registry permissions
by BrowserUk (Patriarch) on Nov 22, 2010 at 14:32 UTC

    More of your trademark, utterly meaningless "advice".

[reply]

      “Trademark” it may be, but “meaningless” it is not.   If you try to fiddle with registry-settings in non-installer programs, you might well find your program swatted-dead by some “anti-virus” bit-cop somewhere.   Here, for instance, if you run such a program ... the program dies, you get logged-off and the corp. security department has to be called to unlock your workstation.

        If you try to fiddle...

        If, when an installer is run, it has the appropriate authority--by virtue of the account it is being run under--to make the changes required, then running a perl program under that same authority, will have those same permissions.

        On the other hand, if the "anti-virus bit-cop" would detect the perl program as unauthorised, then it would also detect an "installer program" as equally unauthorised.

        There is nothing magic about installer programs; they are simply code calling APIs.

        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".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom