DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 63KD6udK4116342
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 63KD6udK4116342
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=QoiALLD8
X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D86214D108D8
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1776690415;
	bh=vYB6cjMP66lpnz3hy48imXXSh0UhQuyYeO5P/HImPzg=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=QoiALLD8FEUj7XFa6/cos5MojrZ9BhQYIw3ZRATXN/MhV2KW/BIN8YQQ9Rwe547lC
	 7pO/ItNYqdwtGouxs6TLd5t9wvtmzH8MqEAq5QbxxEK+jqR/8X/d8FujeyK4i80aO4
	 vKL6uwJIKauXww0CgSnFQ3N48GWX+IDCFdJciC1M=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CAFC44B35883
Date: Mon, 20 Apr 2026 15:06:08 +0200
To: cygwin@cygwin.com
Subject: Re: Unexpected "setfacl: illegal acl entries"
Message-ID: <aeYkwLMJA7DAo1Ly@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <103818205.20260420013503@yandex.ru>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <103818205.20260420013503@yandex.ru>
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

On Apr 20 01:35, Andrey Repin via Cygwin wrote:
> Greetings, All!
> 
> I'm receiving this unexpected message when trying to edit the directory ACL:
> 
> >> [C:\Programs\Cygwin\bin]$ setfacl -m user::rx .
> >> setfacl: illegal acl entries
> 
> But then I'm trying this
> 
> >> [C:\Programs\Cygwin\bin]$ setfacl -m user::r-x .
> 
> and it succeed.
> 
> To the all of my knowledge, ACL bits can be specified in any set or order.
> 
> Even the `setfacl -m user::wXr` command is correct.

Our setfacl doesn't support that yet. It was originally designed after
the description of the Solaris setfacl and the man page of that didn't
mention that the perms can be in any order.  Just reading the Linux man
page and it, too, doesn't mention that an arbitrary order is ok.  To my
knowledge there's also no actual standard defining the exact way how
setfacl operates.

Our setfacl doesn't support 'X' yet.  Actually I just read about it for
the first time :}

I add that to my TODO list, but don't expect anything for 3.6 at all,
and for 3.7 any time soon.

As always, patches to the cygwin-patches maling list are, of course,
welcome.


Corinna

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
