Registry keys not only accessible when user
Larry Hall (Cygwin)
reply-to-list-only-lh@cygwin.com
Tue Oct 9 21:58:00 GMT 2012
On 10/9/2012 4:51 PM, julien2412 wrote:
> Larry Hall (Cygwin) wrote
>> On 10/9/2012 2:37 PM, julien2412 wrote:
>>> How to workaround launching Cygwin with admin rights and still access
>>> these
>>> registry keys?
>> Windows won't let programs run by unprivileged users manipulate this
>> registry hive. If you only need read access, you will need to change the
>> configuration tool to drop the permissions it does not need. If you do
>> that, then what you're doing should work. Note that this isn't Cygwin-
>> specific. You'd see this same issue even if you removed Cygwin from the
>> equation.
>
> Sorry for having talked about the configuration tool, it's misleading here.
>
> In Cygwin, if I just test "ls /proc/reg*", it shows there are
> "/proc/registry", "/proc/registry32" and "/proc/registry64"
>
> Now if I just run an ls /proc/registry/<abbreviated
> HKLM>/SOFTWARE/Microsoft, I can see the registry keys I quoted only if I
> launch Cygwin with admin rights.
Oh, OK.
> Anyway, I noticed that with regtool, everything was ok.
> Is "regtool" the recommanded way to access (in read only) registry keys? And
> so we should avoid to run things like this Perl script line:
> open($fhandle, "/proc/registry/$key") )
Whichever works. ;-)
Thanks for the clarification.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin
mailing list