X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Matthew Woehlke Subject: Re: Execute permission not set when creating files Date: Tue, 28 Oct 2008 17:22:22 -0500 Lines: 25 Message-ID: References: <8482EC0DCFAD453DB586BF083A37715C AT ra> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.16) Gecko/20080723 Fedora/2.0.0.16-1.fc9 Thunderbird/2.0.0.16 Mnenhy/0.7.5.0 In-Reply-To: <8482EC0DCFAD453DB586BF083A37715C@ra> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 John Cooper wrote: > I've just upgraded to the latest version of Cygwin (1.5.25-15) and found > that the execute bit is not getting set when I create files: > > $ umask 'u=rwx,g=r,o=r' > $ touch a > $ ls -l a > -rw-r--r-- 1 John None 0 Oct 28 21:42 a > > (the execute permission also doesn't get set when I use the default umask > 0022). I don't think I've met a POSIX-like system yet that automatically creates things with any +x bits set. From a security perspective, this makes sense; the user must request something be executable before it can be executed. (Some things, e.g. gcc, will add the +x when it makes sense.) Windows is unique (or at least unusual) in making things like "My Wish List.doc" and "Pamela Xmas.jpg" executable. -- Matthew Please do not quote my e-mail address unobfuscated in message bodies. -- ESNR: signal to noise ratio too low (try a mailer without disclaimers) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/