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=DdeSF0e+UWa7twKRl2zSzMqtGb2YPjMnBlTISmk14km8HrZFb3cnK
	eEsgAYm+QY0BIQ+YrRNNyqSYM2U8igWmBpASJQfg3O3Oe0gYr7GmM0H9BcJYEZsN
	PunYE+H5IgvRsu7fb8mHhHEmEbjnuQ4VY/iu8L8shuTewREUp87zo4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sun, 6 Sep 2015 13:44:44 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Group Permissions on root folders problem (Windows 10 TP build 10061)
Message-ID: <20150906114444.GA27066@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAMH9mcFEL3mao+m-DEYM84kC1HOPeSBpZXD+mDf0USobF9oY7g@mail.gmail.com> <CAMH9mcFOKjvjiFvvk1ju0ZxBDK28MaktdnYwj5_CjvbgnpVO4A@mail.gmail.com> <20150616155843.GE31537@calimero.vinschen.de> <20150905155916.8403bea8d4f631c1f7a314e3@nifty.ne.jp>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt"
Content-Disposition: inline
In-Reply-To: <20150905155916.8403bea8d4f631c1f7a314e3@nifty.ne.jp>
User-Agent: Mutt/1.5.23 (2014-03-12)

--pf9I7BMVVzbSWLtt
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sep  5 15:59, Takashi Yano wrote:
> Hi Corinna,
>=20
> Is there any progress regarding this problem?

Considering that I had entirely forgotton about it, no.

> I recently encountered the same situation. After some trials,
> I found this problem occurs if the account, on which cygwin
> setup is executed, is a Microsoft account. This does not occur
> if the account is a local account.
>=20
> Above is true for both:
> a) Group permissions on root folders
> b) Creating sshd service using cyg_server
>=20
> I would be happy if this information helps you.

Not really.  For privacy reasons I'm not using Windows accounts, so it
would be really nice if somebody could track this down.

The group permission problem is easy (and I'm wondering if it really was
such a bright idea to let user SID =3D=3D group SID slip through in Cygwin,
rather tnan  sticking to the former idea to change the group SID to
"Users" in this case).  csih needs a patch to not check for the group
x bit if user SID =3D=3D group SID.

However, I have not the faintest idea why the cyg_server stuff doesn't
work.  Anybody willing to track this down in the csih helper script?


Corinna

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

--pf9I7BMVVzbSWLtt
Content-Type: application/pgp-signature

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

iQIcBAEBCAAGBQJV7CcsAAoJEPU2Bp2uRE+gl4AQAICbxm9xGjsXRgyYbs+NQ8LS
LXt6RyNlRPtnmmYd1efqR1BcKgMlefBswJJR876V1TnaYPq7pVYiDrxWmdwn5i/i
l8Shr4jHBAnndsD97bwVRJqnHCETzHJfcTrpJpkPB57OpbyOuq7SQIiURq6apBvi
wu4TQvaOlzwz5FTcZLU0drsYjtZTxgnMJvr+dYDf7mmFrH9ctHBzHMrWw6PRNmb+
85poL8G4MG0s3Vax9xd1SSCCcCPLfBEqJrCsvnjqwlSI+gVZWkFoq6LQDlfrOhlD
7FvSLkep/Ny3mMgkBe1rX7HW+33QjFDQpa73uRQqYZYhZsooet7bgQ6BqCFjfCBa
1Y/86CDN7Vazx6LeQGyqo2veBo2sKDwkh0piivqxEBw6RjlSIofdsPQD06tm5kY5
HT8rl03IqZo1lHmN1mVNfg5+qqEzAM+f/uaXCpezVZbbIK0JsXsYOiS/qtbHdx+0
pGDAuKvX7Aiw2y/uE0IQjbV8ks+QjFWAhla6N+kbqG9CxB2xBwLUar2vDBCm5DDY
8xC9MnwC7W9uk8PLFSDFhcD+stbvz1reNA20QjVi2gGKWkpKpJTdh2/f7n0BaFA6
OrYStk6BO9z4t2nc8DQ1uCI9mKY/qXwQqkSugB4H2Ov3pVQMy3sgabwdVmEDh0na
KrUTngzAQ+ZOkZ8aVFXI
=+a7V
-----END PGP SIGNATURE-----

--pf9I7BMVVzbSWLtt--