This is the mail archive of the
mailing list for the Cygwin project.
Re: Problems with screen on Windows 10 Preview system
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Stephen John Smoogen <smooge at gmail dot com>, cygwin at cygwin dot com
- Date: Sat, 2 May 2015 21:58:26 +0300
- Subject: Re: Problems with screen on Windows 10 Preview system
- Authentication-results: sourceware.org; auth=none
- References: <CANnLRdjiHWKS8VBzTs0dh5K3h+3raffCeDN-JBu+HHic+FduVA at mail dot gmail dot com> <20150502134701 dot GC12723 at calimero dot vinschen dot de> <CANnLRdgGktkROkekReY9wWmdybQgMntY+wRhuctj=MYTUZ4NMw at mail dot gmail dot com>
- Reply-to: cygwin at cygwin dot com
Greetings, Stephen John Smoogen!
>> Either Cygwin sets the group permissions in the POSIX permission
>> attributes to the same value as the user permissions, e.g.
>> then security-sensitive POSIX applications will complain that the
>> permissions are too wide-open.
>> Or, Cygwin sets the group permissions to 0, e.g.
>> Then, apparently, screen complains.
>> There would be a third way, which is, to spill the "other" permissions
>> into the group permissions, in my example:
>> That should work, but needs YA patch to Cygwin and needs some testing.
>> Bad timing right now (vaca).
>> Workaround: Set the primary group to the affected files explicitely to
>> an existing group which is in your user token. That would typically be
>> the group "users", e.g.
>> chgrp users /tmp/uscreens
>> should work, and then you can chmod it and screen should stop
> Thank you for answering while you are on vacation. I am going to see
> if a /etc/passwd and /etc/group entry to better fix that long term.
I think, http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-desc
will be a better way to go. Assuming "MS accounts" work the same way.
With best regards,
Saturday, May 2, 2015 21:56:47
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple