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:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; q=dns; s=default; b=hXgyed3 5CiKRssUz3UxVLpXBFKX0l9j+/zpoETR9g+M6oy2g4BLBOmpof7EKQtrKSdBM0BX EqsMYb7JZjrJHtDVZjT4p+kqpRjb9uu+4lI4Yqw1KWiEX/3ul0sYRqhAu9NitwLu OjV3HH/GM8tTIaj36k17POQUrm18UDjJlVLU= 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:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; s=default; bh=5XtvbuC/F43Ld 4XttFs2mRiKCXg=; b=UuepTmVmcsAm2P5+OpT7sXhAvhfYxi3jAzzHJ6EaHNl/a DSwatqHafN4cGgcGo3ccIGSWlqmA000D3Qa4MKGYjQsg7jDg8g/q6UVnas9s7BOj 63b3nGwh9Lext9eAbn/7kqrxr12PLWpVfbsJDgaqunjiM+YP6cUAZ9UBg4VeBk= 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=0.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-oi0-f48.google.com X-Received: by 10.60.58.137 with SMTP id r9mr13161864oeq.1.1423515672736; Mon, 09 Feb 2015 13:01:12 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20150209162607.GE5633@calimero.vinschen.de> References: <20150209162607 DOT GE5633 AT calimero DOT vinschen DOT de> From: diod lightbulb Date: Mon, 9 Feb 2015 22:00:52 +0100 Message-ID: Subject: Re: ls not in sync with chmod (weird problems with file permissions) To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes On 9 February 2015 at 17:26, Corinna Vinschen wrote: > On Feb 9 16:37, diod lightbulb wrote: >> HI all, >> >> Maybe this is a regression. This is linked to the problem reported in >> this other thread https://cygwin.com/ml/cygwin/2015-02/msg00100.html . >> I took notice of >> it right after I updated cygwin (setup.exe 2.867) today. > > Does https://cygwin.com/faq/faq.html#faq.using.ssh-pubkey-stops-working > help? > > > Corinna > Hi, Corinna, Sorry, I didn't get the time to completely check the other thread as I had a lot of troubles subscribing to the mailing list, your answer was already there.Thank you, this answer is spot on. To sum up (please correct me if I'm wrong), here is how I understand what happened: a- the Posix file permissions under my home directory remained pretty much the same as those files/directories were created by cygwin-related apps b- After your fix, the ACLs struck back in non-cygwin generated files. Unfortunately, even if I took care chmod'ing (644) nearly all my files, the ACLs got rid of all that. All I can do now is apparently to run all my pre-existing files thru setfacl -b (I like to keep my files with 644 permissions) followed by chmod. I just have to figure out how to retain the execution bit for the few select executables that need it. However, I'd like to ask somthing else, is there a way to make newly created files outside my home to respect my umask? I just tried touch still buggy; ll stillbuggy reports -rw-rwxr--+ while stat -c " %a %u %g" stillbuggy gives back " stillbuggy 674 1000 545. So ACL still seems in effect on both my D: and E: drives except my cygwin home directory. Any hint welcome. Regards, Green -- 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