X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=x3uNK7Befm47RSJcB5znHgMEWiS3s/DBDd+OHpo62GUReHxfe7dvm daa/ZV+R4yWSYANjajjuD8z3O2T4zanYOIVImK/CCVnvs4FZ7u6sXb0EcXoYd1cV NS/DdddiNa1GGJRwjUEymyCRSL5t91ptoTvMX8zoOcqR8o/zaqAHjQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=MTHQBEF/QT6lXrXKiCKiIonFnYU=; b=la+FxOMZpTzjihAqBkcNlxmIwRbp Nfpat0mgBx2uYKUUxLOakz/elYW2sceLS00Xt4jzbUR7dYo8exwBV/78rjOLWId5 wJtzyqZQiuik+k6FEZNVd3liQisBgPjbVlaowbHSqvYmMdCNgYI6/ZDnC/MU3hmt XJmd/uaCq/2gC6U= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-101.9 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,KHOP_DYNAMIC,RCVD_IN_PBL,RDNS_DYNAMIC,USER_IN_WHITELIST autolearn=no version=3.3.2 spammy=0.2, perms, Wolff, wolff X-HELO: calimero.vinschen.de Date: Mon, 21 Dec 2015 16:01:19 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.4 Message-ID: <20151221150119.GG4034@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20151023122230 DOT GG5319 AT calimero DOT vinschen DOT de> <20151023122519 DOT GH5319 AT calimero DOT vinschen DOT de> <5677FD30 DOT 20502 AT towo DOT net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TeJTyD9hb8KJN2Jy" Content-Disposition: inline In-Reply-To: <5677FD30.20502@towo.net> User-Agent: Mutt/1.5.24 (2015-08-30) --TeJTyD9hb8KJN2Jy Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Dec 21 14:22, Thomas Wolff wrote: > On 23.10.2015 14:25, Corinna Vinschen wrote: > >On Oct 23 14:22, Corinna Vinschen wrote: > >>On Oct 23 11:06, Achim Gratz wrote: > >>>I don't have much time to test it right now (and won't have any time a= t all > >>>next week), but so far things look good. The problem with the 0.2 test > >>>version with UID/GID mapping and not recognizing the primary domain in= some > >>>cases is gone (might have been a fluke anyway). Correlating the outpu= t from > >>>getfacl and icacls still requires some mental gymnastics, but I didn't= find > >>>any obvious errors in the mode bits and ACL so far, which means that t= hings > >>>like rsync (and some file tests) will now return the correct results f= or the > >>>cases I've looked at. > >>You won't believe how grateful I am having you testing this. Thank you! > >> > >>Would you mind to read the comment at the start of sec_acl.cc? > >https://sourceware.org/git/?p=3Dnewlib-cygwin.git;a=3Dblob;f=3Dwinsup/cy= gwin/sec_acl.cc;hb=3Da8ec1e804ee9ba2d6f8304731e593dcf167c9836#l27 > > > >>I'd be > >>very interested in learning if the description is meaningful enough to > >>other developers. I also fear we need to have an improved documentation > >>explaining how this works and what NOT to do, e.g., reorder ACLs :| > Sorry for the late response... > The description is mostly meaningful. Just the coexistence of X and X_OBJ > entries isn't self-explanatory. I think I don't quite understand what you mean. As the developer I'm working under the assumption that the posix ACL description is known (not wanting to explain this from scratch in the sources). - USER_OBJ refers to the owner of the file. Only one such entry exists and is equivalent to the POSIX permission bits for the owner. - GROUP_OBJ refers to the owning group of the file. Only one such entry exsist, same as for USER_OBJ. - USER is an entry for a secondary user. There can be an arbitrary number up to a system-defined maximum of them. E.g, Peter is owner of the file, so he's the one refered to by the USER_OBJ entry. Paul has an additonal entry in the ACL with, say, rw- perms. Paul's permissions are given by a USER entry "user:paul:rw-". - GROUP is an entry for a secondary group. Any number up to a system-defin= ed maximum entries are possible. E.g, the owner is Paul (USER_OBJ), the group is Users (GROUP_OBJ), there's an additional entry for the Administrators group giving them Full Access. This one is a GROUP entry "group:Administrators:rwx". Does this make it clearer? Is there still something missing in the source comment? Thanks, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --TeJTyD9hb8KJN2Jy Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWeBQ+AAoJEPU2Bp2uRE+gmagP/2PsSjLfqfo+3DMt5tPznaGn Nq4BXVNiVmk6wOC0h/ZvtmXIhseS1vsZqr/CB6WtcIhSqr/28l9CJQD5SkEKRSdX TBng0IbJNYlWEfpTeXWQUYzzRocBQSNB1zP/BUI6OH8g/+K0Cza365nETL6+pK4f Q37j9gveeeM+CTN4XgLK6GNp7ckW8zLutsMAecxytLIgwHeMslaKaQlr0QI8V1ux YbBHRqnABVNUXlvGHTl+vuhnQ6Sv4wdYIn+BR2hUOyn4YnAaq1sHMnXvNodohLKw uq2qsViF9Z7a1JOqD1UnRieGoamYJ1zzMjZTZQcYEtDVCZpgWozPk/nz0Z0bjvyv n08+eSSyzZJL0Dp9lO3YNsp3XgjreECpknzCznof9jeZerOSh9uk2hAtLccSPIc2 CiM9+nAjtINYO3nd9Ll5J04Kdb0rlzCyIAV7db6i1Za9ZZIe5sqat89CM2sFdmZz JCBUyXw6tPRS+8zLTyLL381rbua1rvC1qVDXo/NqlAk81XejcS/V29jgYD7WuBSs yufzLIX08WOCusq7Ro5OwB4KWjXD+NwQ1LoCFvfZzVXc0GqQ0BYpIKcQzE+jpl6W 8p8w4moFy4NIGxAKxoHnDphHtFF7jx6FvSQnjlULk1ZkmE3RQec/D8GQyC0u8PqL eP2PpWW+KZ8gWShHN5uO =iimr -----END PGP SIGNATURE----- --TeJTyD9hb8KJN2Jy--