X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8EED53858C83 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca X-Authority-Analysis: v=2.4 cv=OO00YAWB c=1 sm=1 tr=0 ts=62017c1d a=oHm12aVswOWz6TMtn9zYKg==:117 a=oHm12aVswOWz6TMtn9zYKg==:17 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 Message-ID: Date: Mon, 7 Feb 2022 13:07:56 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Subject: Re: Cygwin making files inaccessible? Content-Language: en-CA To: cygwin AT cygwin DOT com References: From: Brian Inglis Organization: Systematic Software In-Reply-To: X-CMAE-Envelope: MS4xfI70dkswkh2n9McuXbBA0RDmJFYhMoaTiP4z9qya3dV4ZnDkho+zFU8aIEQHNuhL1Mw/RtE951929E/GftUWFNg4d7F5zC7G47xl4d9uT5p7FN2W8LHE OXE3p/wqfOzd+dUhvyKYM5Rbwn3soYb7/nyYeegO+Y50YM7MB+OKld7Tzvm0TR+LfMLvgoiZQu3vS9Sh0gpOztefhwbCq8rmT9Q= X-Spam-Status: No, score=-1163.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: cygwin AT cygwin DOT com Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 217K8aTL002652 On 2022-02-06 22:23, Jay K wrote: > I looked at this a while. I tried various recent cygwin1.dlls as there were two ACL changes recently. > Eventually. I noticed the behavior was not the same for every file/directory/volume. Sometimes it worked ok. > Though I think the ACLs still get changed quite a bit: "full" expands to "many". > Of course it has worked plenty for me and everyone else. > Eventually I tried chmod -R 777 * and this seems to have worked. > I speculate that some "bad" Cygwin ACLs got created at some point. > And maybe cacls wasn't deleting them?? That parts seems wierd. Maybe on directories? > Possibly due to those two recent changes, or maybe user error, I don't know. I found after a Windows level restore from backup I had to retweak a lot of Cygwin directory DACLs and directory and file perms; often setfacl -b does the trick if the file perms "+" ACL flag is set; when that doesn't work I use scripts that set: Normal: perms=a+r,u+w,go-w dacl=u::rwx,g::r-x,o::r-x,d:u::rwx,d:g::r-x,d:o::r-x Shared/Sticky/Tmp: perms=a+rwxt dacl=u::rwx,g::rwx,o::rwx,d:u::rwx,d:g::rwx,d:o::rwx Change Windows defaults to Cygwin non-exec defaults: perms=a+r-x,u+w,go-w dacl=u::rwx,g::r-x,o::r-x,d:u::rwx,d:g::r-x,d:o::r-x Add u+x or a+x for executable scripts or commands. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple