Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 12 Sep 2001 22:25:01 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Bash script permissions Message-ID: <20010912222501.M1285@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: <006d01c13bc4$2d570130$391e10ac@dmonknt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <006d01c13bc4$2d570130$391e10ac@dmonknt>; from david@purplebear.net on Wed, Sep 12, 2001 at 02:50:30PM -0500 On Wed, Sep 12, 2001 at 02:50:30PM -0500, David Monk wrote: > I am running the latest net realease on NT 4 and Win 2k. I am having a > problem limiting, from cygwin, the permissions on a bash script so that only > the owner can execute it. > I finally after much fiddling figured out that with the shebang line in the > script, cygwin immediately thinks it's executable by all. If I try any chmod > affecting it's executable status, it's ignored. How can I work around this? > Also, how can this be worked around on Win9x also, as it is planned to > eventually distribute this script set. On NT use CYGWIN=ntsec to use the NTFS ACLs, on 9x forget about it. Where there's no security at all... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/