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=WE4RLhk 1tRI/b9VUAp57aYWvLER+8akgp6wB5nZ3xUNGjGi/Zyi4ZeLcLx2nD2zHvAToMOe 1o68TPL8JDrRlI93IuGrRtPHpT4VFI2UOXYsEHVHrCXqnp7woXGeoqiNDnUj8lZU 6OdxcM8j0QBPF2ynh08433OraVzK/6QsRVNg= 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=1TsEZ5OKr2qoD Y885JiBkTzO/7s=; b=tqceuXvlEk1QLvJ87yT+/W7SN7rWpNvrLoNDIkqr+3iuj 6jnGxnt3aFY6y5zXgCfqJb9RWaxRP7ooXWkoyDabjalrHQgYf3HAAY81j1pL8alk TTOT2yWwElkq/FptEH/LN9cD0KCIDg29fA1TEC2fgIJXVD50QvmaaGiwKJqQrI= 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.3 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-la0-f50.google.com X-Received: by 10.112.234.199 with SMTP id ug7mr860418lbc.116.1443148760427; Thu, 24 Sep 2015 19:39:20 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <56044D87.1070409@cornell.edu> References: <560366EE DOT 5020207 AT tlinx DOT org> <56043BA4 DOT 7040405 AT tlinx DOT org> <56044D87 DOT 1070409 AT cornell DOT edu> From: Greg Freemyer Date: Thu, 24 Sep 2015 22:38:40 -0400 Message-ID: Subject: Re: cygwin potentially corrupting permissions? To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes On Thu, Sep 24, 2015 at 3:22 PM, Ken Brown wrote: > > > 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.) I just posted this, but it looks like directories created in cygwin have reasonable ACLs, but directories created via "File Explorer" are bizarre. Where bizzare is defined as: $ getfacl /cygdrive/c/Test-dir-created-in-file-explorer/ # file: /cygdrive/c/Test-dir-created-in-file-explorer/ # owner: GAF # group: None user::--- group::--- group:root:rwx group:Authenticated Users:rwx group:SYSTEM:rwx group:Users:r-x mask:rwx other:--- default:user::--- default:group::--- default:group:root:rwx default:group:Authenticated Users:rwx default:group:SYSTEM:rwx default:group:Users:r-x default:mask:rwx default:other:--- Here's getfacl for C:\ $ getfacl /cygdrive/c # file: /cygdrive/c # owner: TrustedInstaller # group: TrustedInstaller user::--- group::--- group:root:rwx group:Authenticated Users:--- group:SYSTEM:rwx group:Users:r-x mask:rwx other:--- default:user::--- default:group::--- default:group:root:rwx default:group:Authenticated Users:rwx default:group:SYSTEM:rwx default:group:Users:r-x default:mask:rwx default:other:--- Is that what others have? fyi: I just realized I installed "System Mechanic" around the time I started seeing problems. It is installed on both of the machines having issues. I wonder if it adulterated my ACLs in an attempt to make my machine safer? Thanks Greg -- 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