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=XteSzxMDFvFwSWFdQWDGIizwNKgarr56q2o27HEcVJixz3b7jSxXk
	hPw3yKc+D9ijNAJPLTkxZEtyFq8EogL9if1IHSArME2uUvaKmMX7y7hHIEA3ld2K
	vCtE9nJxf09BGO1HswKaIMI9oTkG7dljyEFY+iMwL2NXlFILBmH2XY=
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=pYwIVpgdVr7fCWqfOtnbrlNcFPc=; b=AfPzFk9BCedIWzfrM+soeYcAFvDf
	lrHjwF6RZtJdqIU8rWDjIptnFIJen8PCPFO+CSD7A7d7Odn8yy1IrN/HSeI26SPM
	NF7uCQp1ZYd/w6ax9mWqyCnpanPBsKCns+I8K+ZzR0N0Vw4Ie+vJUG8wzuZgbwHT
	QX7bwnp1b2feSeQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-96.6 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_PBL,RDNS_DYNAMIC autolearn=ham version=3.3.2 spammy=H*i:sk:5715448, H*MI:sk:5715448, H*f:sk:5715448
X-HELO: calimero.vinschen.de
Date: Tue, 19 Apr 2016 09:57:00 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Permissions change concern
Message-ID: <20160419075700.GA26794@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5712F224 DOT 7070308 AT cs DOT umass DOT edu> <20160418101803 DOT GM24565 AT calimero DOT vinschen DOT de> <5714DDA9 DOT 3030002 AT cs DOT umass DOT edu> <20160418185553 DOT GB31378 AT calimero DOT vinschen DOT de> <5715448F DOT 8080204 AT cs DOT umass DOT edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X"
Content-Disposition: inline
In-Reply-To: <5715448F.8080204@cs.umass.edu>
User-Agent: Mutt/1.5.24 (2015-08-30)

--LZvS9be/3tNcYl/X
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr 18 16:33, Eliot Moss wrote:
> On 4/18/2016 2:55 PM, Corinna Vinschen wrote:
> >On Apr 18 09:14, Eliot Moss wrote:
> >>On 4/18/2016 6:18 AM, Corinna Vinschen wrote:
> >>>On Apr 16 22:17, Eliot Moss wrote:
>=20
> >Your example looks like 775.  But even then, the actual permissions
> >depend on the mode bits given to the open(2) call, which are usually 666
> >in this echo example.  The resulting perms should be 664.
>=20
> Thank you -- I am convinced and agree, and that is what I get.
>=20
> >Cygwin also takes the umask value into account if the newly created
> >ACL only contains default POSIX permissions.  That's not quite correct
> >in terms of POSIX 1003.1e draft 17, but in contrast to Linux, Windows
> >directory ACLs practically always have default ACEs, so we have to
> >compromise a bit, or umask just has no effect at all.  I fixed a
> >problem with the permssion handling in case a mask value is present, but
> >that shouldn't matter in your case.
> >
> >>2) If the directory has g+s set (visible from -s- in the flags shown
> >>    by getfacl), the directory's group is Cygwin, and my primary group =
is moss,
> >>    then the file gets created with group moss, not group Cygwin (which=
 is
> >>    what g+s is supposed to mean, right?)
> >
> >There was still another bug in the same code snippet which disallowed to
> >set the special POSIX bits S_ISVTX/S_ISGID/S_ISUID under some
> >circumstances, but apart from that what you describe works for me if the
> >bit is set in the parent dir and the parent dir inherits entries.
> >
> >But this only works if you create the file with a Cygwin executable and
> >the parent dir has inheritable ACEs.
> >
> >I uploaded another snapshot to https://cygwin.com/snapshots/ to make
> >sure the aforementioned bug can be tested as well.  Please check the
> >latest snapshot again.
> >
> >However, if the s bit (aka S_ISGID) doesn't quite work as desired, I
> >have to defer any solution (if possible) until after my vaca.
>=20
> The g+s bit now works as I hoped/expected. Thanks!     E

Thanks for your feedback!


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--LZvS9be/3tNcYl/X
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXFeTMAAoJEPU2Bp2uRE+gBcUQAIirCxXQroZtwjaVgGlWTZRf
pvWokLZ2h7BObcYCqf0CQM/RwXuylvWiqpRzNREARjpEa3Zocg0UAR37WHAXBsQT
yDV5rLAtelM8Szwdhvw4MghKBRa1uLJ23LksIETnOGQxcS7O6YZoLkpkHxDlHI5z
X4V9lMaGhXb/CsYjiyMqHsn+ZFWYARBahpZhjNDVSqD9bG/OBp4RId1EjdkY1DVL
E1vnvfcHdYaqMOFjnOehvdE1Czi+T5UjHVAbeUGxvqsRK290nCgZXVCpPurNMs8p
2OvaFxHd3LykmlQDNxrK+Ca/tv7mxBDhHAWC59bRGXAMiHRbLoyhwEujXKD5yBvT
pZ8LpYDINSie7V+p1+runuIgWUszSrlbNr0MDSaeWntkmAZXG5aNtEVOYZqKkjf7
4ujbM9c5dz7YLmKffQCfs14+PeZAw9N4/jDgmsfovhYauX+nydhfpjOJkllZpoKx
bJvvvnIYvxcytZ8xEaoU7x2mSowGhXYFUxFhUI8sZuizxoaMNxRNJNvKiYSo/QTg
rvs5J/M6CxVnhcisCcc8VOW5vYipTadsgnpUGWxGeARJ0T5BL8S1DedXbnCCRz57
9iYn2T73v+W6XCgZEJVjfdIv0e/ZHwgXLMO+d0LWwZKkD9NQJU43lDwoBVFvB9iJ
XNB8XaDhOEN9w5IegsrL
=Jtsg
-----END PGP SIGNATURE-----

--LZvS9be/3tNcYl/X--