From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: A problem with noacl+umask+chmod result
Date: Thu, 8 Apr 2021 07:48:44 +0200 [thread overview]
Message-ID: <7538d457-4b3e-1e01-d578-7415af235e34@gmail.com> (raw)
In-Reply-To: <CAGHpTBLp33PD_Pa5nGaH-cyfr+0d+Tk=ffqFtBCWP+Jq9VbuPg@mail.gmail.com>
On 07.04.2021 22:47, Orgad Shaneh via Cygwin wrote:
> Hi,
>
> If a filesystem is mounted with noacl, calling chmod to add write
> permissions after umasking this permission doesn't work. Demonstrated
> with command-line and C++.
>
> Did I miss something or is this a real bug? According to umask man, it
> should only affect newly created files and directories, but I didn't
> find anything that relates to chmod.
>
without ACL you can not expect the POSIX scheme to properly work.
see
https://cygwin.com/cygwin-ug-net/ntsec.html
to understand how Cygwin uses ACL to mimic POSIX premissions
next prev parent reply other threads:[~2021-04-08 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 20:47 Orgad Shaneh
2021-04-08 5:48 ` Marco Atzeri [this message]
2021-04-08 20:28 ` Orgad Shaneh
2021-04-09 1:45 ` Andrey Repin
2021-04-09 4:34 ` Orgad Shaneh
2021-04-17 17:11 ` Kaz Kylheku (Cygwin)
2021-04-17 20:29 ` Brian Inglis
2021-04-18 7:13 ` Orgad Shaneh
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=7538d457-4b3e-1e01-d578-7415af235e34@gmail.com \
--to=marco.atzeri@gmail.com \
--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).