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:to:from:subject:date:message-id:mime-version :content-type; q=dns; s=default; b=Ux1rGk+RDKzNCLyp7YwMR8HD8vVlS 0jT1pkin4UfHqX9RAzDdG+9lwSk4cahVJ5KbbKIbw9REnngB7ETepk29hyqjoCsC CqgAslhGZT3GBMPFbKjlneun30SfYFsgnaZnMkBxXCS5wx7oIeZNx98CITw0cWF1 ZPhstOWhfRW/KA= 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:to:from:subject:date:message-id:mime-version :content-type; s=default; bh=elg95i5DQ4GxlyMZaZyApVk1Vo0=; b=wk3 QSR7QcOgJIWTxwwl0ETjW0cZozx2ET0ZFYcJwBIfXTZ9BUizezWA3PolJ1KHONqH YDViu47PxX9kNzZxZbULKwLBhDRA7vpDPlll4fw9tRCKzD6a1Bk82vewDvSU8WT8 ir/qnFTaA6O8HdgffpOAIAkL4lWY6nKbXdMxJScM= 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=-3.3 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Sebastien Vauban Subject: Security Settings for directories created in Cygwin (+ executable bit on files) Date: Fri, 08 Aug 2014 10:39:42 +0200 Lines: 40 Message-ID: <86wqajxtm9.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain X-Url: Under construction... X-Archive: encrypt User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.92 (windows-nt) X-IsSubscribed: yes Hello, Currently, whenever I create new files from Windows 8 executables (such as Notepad), they're often flagged as "executable", even for text files! I've noticed that such a behavior happens when I create a new file in a directory that has been made FROM CYGWIN (`mkdir ~/test/', for example). Indeed, the permissions of CYGWIN-CREATED DIRECTORIES seem very weird: - "Inherited from"... "None"! - "All Users" having "Read & Execute" permission on "this folder, subfolders and FILES"... IIUC, when creating a new file from Cygwin, the `umask' (022, in my case) is respected and new files are not executables then, except if I require it explicitly (via `chmod'). Though, when creating a new file from a Windows executable, Windows inherits permissions from the folder where my file gets created -- hence, an executable permission if the directory was created from Cygwin... How to correct that? Asking Cygwin to stop playing with the Windows ACL, by mounting my personal directories as "noacl"? Well, that means I won't be able to use `chmod' anymore, for setting a script file as "executable", then. And I'll have to use a Windows tool to do so, such as `cacls'. Is it really so, the integration of Cygwin permissions within Windows? Or do I miss something? Best regards, Seb -- Sebastien Vauban -- 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