From: Andrey Repin <anrdaemon@yandex.ru>
To: Sandy <sandy@autonomia.digital>, cygwin@cygwin.com
Subject: Re: How to disable the default bypass of the ACL permissions checking in Cygwin
Date: Tue, 25 May 2021 22:44:48 +0300 [thread overview]
Message-ID: <956270827.20210525224448@yandex.ru> (raw)
In-Reply-To: <172f7dc5-87fd-e008-15d6-0ffd0af29323@autonomia.digital>
Greetings, Sandy!
> We are from the NGO Centro de Autonomia Digital (CAD) based in Quito,
> Ecuador. We have been using Msys2 to test our project Coyim
> (http://github.com/coyim/coyim) in Windows environments.
> The tests are currently running on GitHub Actions, using the Windows
> Server 2019 Datacenter.
> We have one specific test case that is failing because of interesting
> behavior in Msys2. The full description of the issue is available at the
> following link:
> https://github.com/msys2/msys2-runtime/issues/45
> Thanks to the help of one of the Msys2 developers, we found that Cygwin
> bypasses the checking of the Windows ACL permissions when it runs with
> administrative privileges.
That's literally not possible. More likely explanation is that Administrators
group have full access to the object in question.
Please provide the output from icacls and getfacl utilities.
> We would like to know if it is possible to change this behavior of
> Cygwin or at least have his point of view of how we could control the
> permissions even in this scenario.
Unless you can supply an adequate test case, this looks more like
misunderstanding of sort.
--
With best regards,
Andrey Repin
Tuesday, May 25, 2021 22:39:27
Sorry for my terrible english...
next prev parent reply other threads:[~2021-05-25 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 16:44 Sandy
2021-05-25 19:44 ` Andrey Repin [this message]
2021-05-25 20:16 ` Achim Gratz
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=956270827.20210525224448@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=sandy@autonomia.digital \
/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).