From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [Bug] setup regression #2
Date: Mon, 21 Nov 2022 13:47:29 +0100 [thread overview]
Message-ID: <Y3tzYQTFqVNuGuq4@calimero.vinschen.de> (raw)
In-Reply-To: <87r0xwpjlh.fsf@Otto.invalid>
On Nov 21 13:39, ASSI wrote:
> Corinna Vinschen writes:
> > The idea is that the installation tree has POSIXy permissions and
> > administrative users have the right to change stuff. The administrators
> > group is part of the user's token if the process has been started
> > elevated, so, to me, this looks like a natural choice.
>
> As I said, I haven't thought through the implications of doing that. We
> certainly haven't done a security audit or anything like that
> w.r.t. group ownership of the Cygwin tree and permission of the
> installed files.
>
> > The other advantage is that the administrators group has a fixed SID on
> > all systems, while other groups depend on the environment. That goes
> > for the local group "None" just as well as for the "Domain Users"
> > group, etc.
>
> Yeah, a local non-domain installation currently installs as "None"
> ("Kein" in german Windows) and domain ones will have "Domain Users"
...both groups using the same RID is no accident @ MSFT :)
Corinna
next prev parent reply other threads:[~2022-11-21 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 17:14 Achim Gratz
2022-10-01 15:37 ` Jon Turney
2022-10-03 19:23 ` Achim Gratz
2022-10-08 15:18 ` Jon Turney
2022-10-08 16:56 ` Achim Gratz
2022-11-08 16:21 ` Jon Turney
2022-11-09 18:25 ` Achim Gratz
2022-11-13 12:47 ` Achim Gratz
2022-11-20 17:16 ` Jon Turney
2022-11-20 19:05 ` Achim Gratz
2022-11-21 12:32 ` Corinna Vinschen
2022-11-21 12:39 ` ASSI
2022-11-21 12:47 ` Corinna Vinschen [this message]
2022-11-29 21:37 ` Jon Turney
2022-11-30 21:22 ` Christian Franke
2022-12-01 19:50 ` Achim Gratz
2023-02-02 16:00 ` Jon Turney
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=Y3tzYQTFqVNuGuq4@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@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).