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:message-id:from:to:references:in-reply-to
	:subject:date:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=JGd/UVDRngRHCLlW
	hwTPVwwTNSb8qLRd7uraP7NgOfFiXPMdHk/qwTtcWm0DPbEKH7S9qg+HOVaKiGW8
	+juNcrs9/eoUDKd7eih2Ln433FiOUgUG7c426Zjzue10O1WiH1nq7Q3YRi63hJKS
	aaGxgztwmVtixDgnBuesTWqCEEc=
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:message-id:from:to:references:in-reply-to
	:subject:date:mime-version:content-type
	:content-transfer-encoding; s=default; bh=VSUjffj0tIvIMqLESy2Nes
	Ya/X8=; b=cu6XySzhl4sWu2NDGZdYa1KRjSgOkAxWBdTpfSs0mmhxJBNux581D2
	XUkpDuD3LcTOpgc3N+7tLpBU8mJ4IESExrWxV2QE/hZOnp5hMw1p60CB2i+yG7SZ
	hTpNAg/G6z0gj8BCRzLHLPFu/b+nrftO5UJEAU7/9PuBnjFlbcR/4=
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=0.1 required=5.0 tests=BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: BLU004-OMC1S3.hotmail.com
X-TMN: [VMFDW6PTFjAt2bC/aZ8YGUbtlhmDzVqO]
Message-ID: <BLU182-DS2B4F831FEB7E4C1B67330D4440@phx.gbl>
From: "Walter L." <bournenoir AT hotmail DOT com>
To: <cygwin AT cygwin DOT com>
References: <BLU182-W10FB6B21A2AEC90F71470FD4450 AT phx DOT gbl> <154887677 DOT 20150923111537 AT yandex DOT ru>
In-Reply-To: <154887677.20150923111537@yandex.ru>
Subject: Re: Issues encountered with new Cygwin version
Date: Wed, 23 Sep 2015 10:46:57 -0400
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="iso-8859-1";	reply-type=original
Content-Transfer-Encoding: 7bit

Thanks for the quick response!

> > 2) The 'touch' command creates a file with the executable bit set
>
> > [user AT hostname ~]$ touch newfile.txt
> > [user AT hostname ~]$ ls -l newfile.txt
> > -rwxrwx---+ 1 user Domain Users 0 Sep 22 17:21 newfile.txt
>
> > I am fully aware that Windows programs (e.g. Eclipse and Windows
> > Explorer) will create files with the executable bit set due to ACL and
> > NTFS permissions. However, if I 'touch' a file inside an earlier version
> > of Cygwin
>
> Define "earlier" ? The permissions handling has been extensively rewritten
> since 1.7.34.

Probably from a few months ago, but I can't confirm. I've been trying to
figure out how to revert back to an earlier version to verify this. Where
can I find archived versions of Cygwin?

> > the file would be created without the executable bit set (i.e. 644).
>
> Which will then prevent opening it from Explorer by file association.

Not really... In the above example if I 'chmod 644 newfile.txt' in Cygwin,
Windows can still open up the file in notepad by just double-clicking on the
file. Checking the file permission under Windows shows "Special permissions"
checked. It also works even if I remove the ACL bit shown below:

[user AT hostname ~]$ chmod 644 newfile.txt
[user AT hostname ~]$ ls -l newfile.txt
-rw-r--r--+ 1 user Domain Users 0 Sep 23 10:30 newfile.txt
[user AT hostname ~]$ setfacl -b newfile.txt
[user AT hostname ~]$ ls -l newfile.txt
-rw-r--r-- 1 user Domain Users 0 Sep 23 10:30 newfile.txt

At this point I double-clicked on the file in Explorer and it opened in
Notepad, which I then added a line of text and saved it.

[user AT hostname ~]$ ls -l newfile.txt
-rw-r--r-- 1 user Domain Users 18 Sep 23 10:32 newfile.txt
[user AT hostname ~]$ cat newfile.txt
this is a new file
[user AT hostname ~]$

> > To be honest, I can't tell if this is caused by the new version of
> > Cygwin or a Windows Update.
>
> Likely it is caused by the change in Cygwin permissions handling.
> It now correctly inherit permissions in most cases.
>
> > [user AT hostname ~]$ uname -a
> > CYGWIN_NT-6.1-WOW hostname 2.2.1(0.289/5/3) 2015-08-20 11:40 i686 Cygwin

Regards,
~WL 


--
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