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:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=r6LEpX9u5idd9mq2 NrOyip3CrGQZAiEzRaqpE/aBSRpDXqg0mKyMsx60JULeUIA6eGyJXKEmq1XoM5C8 SLCJ/a/ZGo+XAWU8PBH9FpoFYFnrr3aQvCNo6B2McqCQ5r7oaL1Q+R19bshkcFsM iejL1xsx8XSHQhAl1OooBuy3AIQ= 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:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=9//RDoP1UoZ1rLl4wpbSV+ ZR3Zo=; b=TXl1BwM4h9gkJieXXf026M8QCECF4x9rlpT+w2OZ0kmkcxW5GWn8ck wb7PFJtpPa+xXNJOGn1ASUMQVxD5PFAml1te+NrCbd36ANy0AAOwsOtdOHdfkwVA 3tUWbqg+B1Da1IHjm3IsgVwWiQiAVQNisiQwVYlEofwtSfH65eqbg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: limerock02.mail.cornell.edu X-CornellRouted: This message has been Routed already. Subject: Re: cygwin potentially corrupting permissions? To: cygwin AT cygwin DOT com References: <560366EE DOT 5020207 AT tlinx DOT org> <56043BA4 DOT 7040405 AT tlinx DOT org> From: Ken Brown Message-ID: <56044D87.1070409@cornell.edu> Date: Thu, 24 Sep 2015 15:22:47 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 9/24/2015 2:52 PM, Greg Freemyer wrote: > On Thu, Sep 24, 2015 at 2:06 PM, Linda Walsh wrote: >> Greg Freemyer wrote: >>> >>> Linda, >> >> >>> I saved your script as "lsacl.txt". Then I used "cp lsacl.txt it" to >>> make a copy. >>> >>> The copy is permission denied for reading. Basic ls -l shows no >>> difference (as expected) >>> >>> $ ls -l lsacl.sh it >>> ----rwx---+ 1 gaf None 1630 Sep 24 12:05 it >>> ----rwx---+ 1 gaf None 1630 Sep 24 12:00 lsacl.sh >>> >>> But your script does show a difference: >>> >>> $ ./lsacl.sh lsacl.sh it >>> [u::---,g::---,g:root:rwx,g:Authenticated >>> Users:rwx,g:SYSTEM:rwx,g:Users:r-x,m:rwx,o:---/] lsacl.sh >>> [u::---,g::r-x,g:root:rwx,g:Authenticated >>> Users:rwx,g:SYSTEM:rwx,g:Users:r-x,m:rwx,o:---/] it >> >> --- >> Well user 'gaf' (that's you, from the file perms has no access). >> >> So up front, you are denied before anything happens. > > Totally logical, but not accurate. ) > > I am the owner of both "it" and "lsacl.sh." > > For both the user permissions are "---" (why I don't know. I created > lsacl.sh by a simple drag and drop out of firefox.) > > I can cat out "lsacl.sh", but not "it". > > I know "chmod +rw it" gives me access to the file. The problem is > Windows is creating files with permissions like lsacl.sh routinely on > my system. > > Then when I do anything to them in cygwin, the permissions are > modified to block my access. > > I first noticed this because I was exporting CSV files from excel, > then editing them with vi from cygwin. > > On the first edit, all was good. After that, I no longer had > permission to access the file. > > So, either: > > - Windows 7 (on 2 different machines) has started using default > permissions that are bad on their face > > - cygwin is not properly maintaining the permissions when it manipulates a file > > Either way, I would really like a solution that doesn't involve a > manual chmod for every file I create via the normal Windows interface > and which I want to work with it in cygwin. The problem could be caused by the default ACL on whatever directory you're working in. You might consider running 'setfacl -b' and/or 'setfacl -k' on that directory. (Run 'setfacl --help' for more information.) Ken -- 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