delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=2.8 required=5.0 tests=AWL,BAYES_20,BOTNET,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE |
X-Spam-Check-By: | sourceware.org |
Message-id: | <50749DDE.6030905@cygwin.com> |
Date: | Tue, 09 Oct 2012 17:57:50 -0400 |
From: | "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com> |
Reply-to: | cygwin AT cygwin DOT com |
User-Agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 |
MIME-version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Registry keys not only accessible when user |
References: | <1349807869703-93406 DOT post AT n5 DOT nabble DOT com> <507484C0 DOT 3070406 AT cygwin DOT com> <1349815868856-93419 DOT post AT n5 DOT nabble DOT com> |
In-reply-to: | <1349815868856-93419.post@n5.nabble.com> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |