This is the mail archive of the
mailing list for the Cygwin project.
Re: Microsoft Accounts (was Re: Problem with "None" Group on Non-Domain Members)
- From: "Chris J. Breisch" <chris dot ml at breisch dot org>
- To: cygwin at cygwin dot com
- Date: Wed, 07 May 2014 10:09:04 -0400
- Subject: Re: Microsoft Accounts (was Re: Problem with "None" Group on Non-Domain Members)
- Authentication-results: sourceware.org; auth=none
- References: <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> <20140506171626 dot GZ30918 at calimero dot vinschen dot de> <53692867 dot 4060305 at breisch dot org> <20140507115730 dot GE30918 at calimero dot vinschen dot de> <20140507124038 dot GG30918 at calimero dot vinschen dot de>
Corinna Vinschen wrote:
Oh wow. It took me two reads of this to understand it. Caffeine is
finally kicking in, I guess. Unless you just want to hard code the
primary group that mkpasswd generates to "Users" for any account that it
would tend to want to set as "None". That would be some smelly code though.
On May 7 13:57, Corinna Vinschen wrote:
I toyed around with the Microsoft Account a bit more. And here's why
the primary group SID being identical to the user SID is not a good
$ echo $USER
Directory /tmp/uscreens/S-VMBERT8164+local_000 must have mode 700.
$ ls -l /tmp/uscreens/
drwxrwx---+ 1 VMBERT8164+local_000 VMBERT8164+local_000 0 May 7 12:44 S-VMBERT8164+local_000
This will be a problem with other security sensitive applications, too.
Sshd comes to mind.
So I guess we really should make sure the primary group SID is some
valid group, not the user's SID.
"None" is not an option since it's not in the user token group list.
"Users" seems to be the best choice at first sight.
Alternatively we could use the S-1-11-xxx SID of the Microsoft Account.
That would be in line with the idea to have a user-specific primary
And here's a problem which I'm not sure how to solve at all:
When calling the latest mkpasswd, the primary group of the local
user account backing the Microsoft Account will *still* be "None".
The reason is that the local account is just the same old account
as usual. Its default primary group *is* "None".
Only when logging in via the Micosoft Account email address, the
user token will not reflect what's stored in the local SAM, but
will have been changed by the OS as outlined in this thread.
So, when a user decides to create a passwd file rather than using
the SAM/DB code in Cygwin, the information generated by mkpasswd
will not match the user token, and the primary group stored in
/etc/passwd will not even be available at all in the user token.
I have not the faintest idea how to workaround this schizophrenia.
Chris J. Breisch
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple