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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=jd5YtZ4v4cJ1LscZ
	bzbTCbLlCcoAjdIsq5X2VnC4EUVOJxWjVMp0bvS/4GRFA3NB2TOIplbUPujZduWL
	RqHAkKOBhAEXJvkpNqp1GHeXqDUgpExldCq/MQ36EgW/8EhKVwB4bViH7t2jan+P
	EhcIDIxe+TmduyzBA8x3ohnpfXw=
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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=KPDlc5pP40srCzzyD8L+Cg
	s1RII=; b=o4fHpFcmQxHJp4SJXtOJKA92cen+Gtsdd480vd+DpPgZVoEgnujK6k
	papHMwIYN6sXINbtJAQVw5WJPVv5kaWNJLoYsYRFi05zeTGM3dEzfdkvxmz+/P6g
	gH4evK5e73ZyJID0FrtLSl4syNS9o705qgWc3rrXbaNIFiubkngqA=
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:	Yes, score=5.6 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_JMF_BL,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtp.ht-systems.ru
Date:	Sat, 2 May 2015 21:58:26 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<776578550.20150502215826@yandex.ru>
To:	Stephen John Smoogen <smooge AT gmail DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Problems with screen on Windows 10 Preview system
In-Reply-To:	<CANnLRdgGktkROkekReY9wWmdybQgMntY+wRhuctj=MYTUZ4NMw@mail.gmail.com>
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>
MIME-Version:	1.0
X-IsSubscribed:	yes

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.
>>
>>   rwxrwxr-x
>>
>> then security-sensitive POSIX applications will complain that the
>> permissions are too wide-open.
>>
>> Or, Cygwin sets the group permissions to 0, e.g.
>>
>>   rwx---r-x
>>
>> Then, apparently, screen complains.
>>
>> There would be a third way, which is, to spill the "other" permissions
>> into the group permissions, in my example:
>>
>>   rwxr-xr-x
>>
>> 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
>> complaining.
>>

> 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,
Andrey Repin
Saturday, May 2, 2015 21:56:47

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -