www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=2.3 required=5.0 tests=AWL,BAYES_50,DKIM_ADSP_CUSTOM_MED,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_THREADED,NML_ADSP_CUSTOM_MED,URI_HEX |
X-Spam-Check-By: | sourceware.org |
Date: | Tue, 9 Oct 2012 13:51:08 -0700 (PDT) |
From: | julien2412 <serval2412 AT yahoo DOT fr> |
To: | cygwin AT cygwin DOT com |
Message-ID: | <1349815868856-93419.post@n5.nabble.com> |
In-Reply-To: | <507484C0.3070406@cygwin.com> |
References: | <1349807869703-93406 DOT post AT n5 DOT nabble DOT com> <507484C0 DOT 3070406 AT cygwin DOT com> |
Subject: | Re: Registry keys not only accessible when user |
MIME-Version: | 1.0 |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 |
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. 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") ) Julien PS: "uname -rs" gives "CYGWIN_NT_6.0 1.7.16 (0.262/5/3)" -- View this message in context: http://cygwin.1069669.n5.nabble.com/Registry-keys-not-only-accessible-when-user-tp93406p93419.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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 |