DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=AEi0GxLMP7sYKvcFu+yDJP1GfrXP
	h53XYEZEPUaqPr5QqqAf6mSaFNcpVVBJ1ucN813ixLhd+809MS5d3H0+dSfMZeRr
	kO/aTdoTWHAsGINBWz+iySZzWx+GzEzwsnmAL3SsN4ccmAawA3PxkVc2SGdfqDge
	dQVMQzZ5mPV0UMg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: [TESTERS needed] New POSIX permission handling
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <20150410100703.GA4401@calimero.vinschen.de>
Date: Fri, 10 Apr 2015 15:13:42 -0600
Message-Id: <F9F79D9B-8AA5-4911-96D7-22FA4795CEA0@etr-usa.com>
References: <20150410100703.GA4401@calimero.vinschen.de>
To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On Apr 10, 2015, at 4:07 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> 
>  This should help in Cygwin<->Windows interoperability.

That’s pretty vague.

Would you care to list some specific expected improvements from this change?  Are there known problem scenarios in the current world which we can test both ways, which should behave differently under the new DLL?

For instance, does it fix the well-known problem with chmod 600 ~/.ssh/* resulting in mode 660 until you kick the ACLs around a bit?
--
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