From: Ken Brown <email@example.com>
Subject: Re: Unexpected permissions for home dir install
Date: Wed, 31 Aug 2022 15:16:09 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 8/31/2022 2:42 PM, carbonfiber123irc carbonfiber123irc wrote:
> I have experienced the following unexpected default
> behavior when installing cygwin inside my home directory.
> Using the --no-admin option and choosing "just me" in the setup.
> As user1 when installing cygwin to:
> Then all the directories and files have the read and execute
> permissions for the "Everyone" SID.
> This means a user2 on the same system can read files inside
> It also means that user2 can use stuff in the cygwin install
> such as bash, even though I did not intend for that to be available
> to user2.
> The above applies both to the newest cygwin setup from the cygwin
> website as of this writing, and also to the 2.921 setup.
> I have worked around the issue myself by setting the permissions
> manually after the install. So I am just writing this to inform
> you that I found the behavior unexpected, and then you can determine
> if you consider it a bug or not.
Setup displays the following text below the "Just Me" button:
Cygwin will still be available to all users, but Desktop Icons,
Cygwin Menu Entries, and important Installer information are
only available to the current user. Only select this if you
lack Administrator privileges or if you have specific needs.
This is consistent with what you observed.
next prev parent reply other threads:[~2022-08-31 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 18:42 carbonfiber123irc carbonfiber123irc
2022-08-31 18:42 ` carbonfiber123irc carbonfiber123irc
2022-08-31 19:16 ` Ken Brown [this message]
2022-08-31 19:59 carbonfiber123irc carbonfiber123irc
2022-08-31 19:59 ` carbonfiber123irc carbonfiber123irc
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).