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=KsXBCA/wAYfFCbL1VToJZQsAJFjmFUg/myv91lT4y2Gu7OqaV7kd3
	dpUZTMhvfcPozbzmCFJlqocBK466Su6WTNPAxU8kXNR5YleM5yqO7TBiE6QN5fhl
	gRCxXYQJVHcXi6ehGmmf2wYuMP7RIpngl0dHtqD7HiHE8wu356w4GY=
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=i2RpVuvWjyF9v0xTVMloJitaojg=; b=aR+sXmu51vBoJQN0V3QFEJMCGARz
	O26x6iVFBHFROyZipDFHkoPqp2LWwPqx9HLhXv6guvqEEYFRja5FgvDTWkgnFrlb
	9czr2TVuZ1xOhzE+5ClChdS25/z/XRkEWCl9Gb/S/4MIDyJcSIeFMtxqFis8RNHb
	G9hfTu2HqGsjNTQ=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Tue, 6 May 2014 19:16:26 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Microsoft Accounts (was Re: Problem with "None" Group on Non-Domain Members)
Message-ID:	<20140506171626.GZ30918@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20140505135928 DOT GK30918 AT calimero DOT vinschen DOT de> <53679D5C DOT 5030209 AT breisch DOT org> <20140505144745 DOT GA6993 AT calimero DOT vinschen DOT de> <5367ACED DOT 40409 AT breisch DOT org> <20140505154230 DOT GB7694 AT calimero DOT vinschen DOT de> <5367B990 DOT 8050907 AT breisch DOT org> <20140505165723 DOT GM30918 AT calimero DOT vinschen DOT de> <5367DEE5 DOT 5010407 AT breisch DOT org> <20140506125203 DOT GO30918 AT calimero DOT vinschen DOT de> <53691564 DOT 1070200 AT breisch DOT org>
MIME-Version:	1.0
In-Reply-To:	<53691564.1070200@breisch.org>
User-Agent:	Mutt/1.5.21 (2010-09-15)

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

On May  6 13:01, Chris J. Breisch wrote:
> Corinna Vinschen wrote:
> >Other than that, I'm open to discuss the necessity(?) to override
> >the primary group by default.  But, in fact, I'm not sure this really
> >makes sense.  Linux systems default to creating a user-specific group
> >account and using that as the user's primary group for years.  The
> >Windows Account technique isn't quite as nice, but admittedly, it
> >does its job just as well.
>=20
> Yes, I've experienced that on Linux, but I don't recall having these
> file permission issues there. Perhaps I just never noticed though.

No, it *is* different,  On Linux you get a user account called "Chris"
and a group account called "Chris", and they are different because users
and groups are totally different beasts on POSIX systems.  You can have
a user with uid 42 and a group with gid 42 and they are still different.

On Windows, users and groups are identified not by uid/gid, but by
their SID.  The SID is a unique value, but other than that, a SID can
be a user or a group and in lots of cases Windows doesn't care.
A group can be owner of a file and a user can be the group of the file,
it just doesn't matter to Windows.

The permission "problem" you're seeing is a result of that.  Your user
*and* your primary group are both your user's SID.  Therefore the same
account is user and primary group at the same time.  Therefore, if
the file is created, it gets created with an ACL with user and group
being the same account.  Therefore the POSIX translation of the user
and group permissions on the file are always the same.

Does this clear it up?


Corinna

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

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTaRjqAAoJEPU2Bp2uRE+gTSkP/RVsttrMLkFjZ96rY0AgJrgM
2FEl7piDRjzEj56R7J7+lSV+3lfYWwwAWeXVUUasHYRMr5V5HoZvJspPLRx0LodH
Up89JUiMpqjgAVqLvvGMUK3dW86iTycti7AYxeMqiOCgboII99ihKBnRGiYtTTdL
RNIZfMsA2WWNpfk4+JILuJDGgVbXbvPHtQozKy08whF9Wl35h5x6PjSuY9do1aZg
EnBB4TqZNVWJIVL4sYI97v+Kgo3QFWhp1JwzAeZZ5uFksija2XMz/9PINZJWZ4wk
8w0ZxkvctHDSI3N+5AuRTIOF0vQhDtFriKKX+TXARD9FZGydOA7tVFo/5Ig2r3BN
CFNfqNERW+qk/4FDVmqgkzJzaJJNtkSTRrsu/sgnOFRoLDSMj9sXwE8nWiBF+Gj6
MoHVjy2ETEEnVmTWR83WhumL3+CFWxeh6/xIHaVP2fC3W0RlXy9QXd9vW7NBAwea
PUtG6eau9R35PwuRG+Ro9da3SY7CcMl1gU4gKIgeJZ2V2uYWC74EBkBQc/76Gj6g
CRQe/jXFw2CC+QAvkn8P5TVoyhQOlBDf3ic0XzOaIJJ7XOUho2UIe22Sa2T6FlAW
3F9lLj82TZEN4rPsUDT+Xl0bvO2i9j5GlPh+cDKqGQjVYcO6wVHXhBtE2iTXX71l
gMn7nyhhH1Vfargvyqt9
=FXBA
-----END PGP SIGNATURE-----

--ngiTnHdmUEG79yp6--

- Raw text -