public inbox for
help / color / mirror / Atom feed
From: Corinna Vinschen <>
Subject: [newlib-cygwin/cygwin-3_3-branch] Cygwin: ACLs: don't set indicator for default ACEs prematurely
Date: Tue, 25 Jan 2022 19:05:32 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=7d1e87cd76a920824507ff62164e8dbf3dcb8232

commit 7d1e87cd76a920824507ff62164e8dbf3dcb8232
Author: Corinna Vinschen <>
Date:   Tue Jan 25 19:53:40 2022 +0100

    Cygwin: ACLs: don't set indicator for default ACEs prematurely
    Commit a2bfe7cae61a introduced a change ignoring default ACEs on files
    to come up with a valid POSIX ACL, reflecting the Windows ACEs actually
    making sense on files.
    However, if CREATOR OWNER or CREATOR GROUP ACEs - both only making sense
    as default ACEs - are found in the ACL, a value indicating the presence
    of default ACEs gets set, even on files.  This in turn breaks a
    subsequent integrity check and get_posix_access returns EINVAL.
    The code path handling default ACEs on directories sets this indicator
    anyway, so don't set it just because one of the above SIDs are found.
    Fixes: a2bfe7cae61a ("Cygwin: ACLs: ignore *_INHERIT flags in file ACLs")
    Signed-off-by: Corinna Vinschen <>

 winsup/cygwin/ | 2 --
 1 file changed, 2 deletions(-)

diff --git a/winsup/cygwin/ b/winsup/cygwin/
index 98d2391b1..32edf0d32 100644
--- a/winsup/cygwin/
+++ b/winsup/cygwin/
@@ -850,14 +850,12 @@ get_posix_access (PSECURITY_DESCRIPTOR psd,
       else if (ace_sid == well_known_creator_owner_sid)
 	  type = DEF_USER_OBJ;
-	  types_def |= type;
 	  saw_def_user_obj = true;
       else if (ace_sid == well_known_creator_group_sid)
 	  type = DEF_GROUP_OBJ;
-	  types_def |= type;
 	  saw_def_group_obj = true;

                 reply	other threads:[~2022-01-25 19:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* 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).