From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: [PATCH] root-uid: new module
Date: Wed, 27 Jun 2012 13:58:00 -0000 [thread overview]
Message-ID: <4FEB1189.80902@cwilson.fastmail.fm> (raw)
In-Reply-To: <4FEA5161.6010503@redhat.com>
On 6/26/2012 8:18 PM, Eric Blake wrote:
> Broadening the question, does the cygwin community have advice on the
> best implementation of a function that returns true if the argument is a
> uid with full privileges (for example, if the uid is a member of the
> Administrator group, and can therefore read files in spite of chown()
> disabling all the read permissions)? We're trying to improve gnulib
> (and therefore coreutils, findutils, tar, ...) to use an
> implementation-appropriate check rather than the more traditional
> hard-coded check of uid==0, since that doesn't quite work everywhere.
There is some support code for doing various Win32-related group/user
analysis like this in cygwin's login package. The files you'd be
interested in -- winsec.c and winpriv.c, along with test_winsec.c --
were written by Chris Rodgers, me, and I'm sure Corinna contributed a
few patches along the way. Those three files are under slightly
different licenses, but are MIT/X-ish.
--
Chuck
--
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
next prev parent reply other threads:[~2012-06-27 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FEA4A72.8090003@cs.ucla.edu>
[not found] ` <4FEA4D53.3090409@redhat.com>
[not found] ` <4FEA4FDB.5030105@cs.ucla.edu>
2012-06-27 0:19 ` Eric Blake
2012-06-27 7:54 ` Corinna Vinschen
2012-06-27 14:13 ` Paul Eggert
2012-06-27 13:58 ` Charles Wilson [this message]
2012-06-27 14:13 ` Charles Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FEB1189.80902@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).