Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: "Krzysztof Duleba" <krzysan AT skrzynka DOT pl>
Subject:  Re: perlcc and permissions
Date:  Sun, 28 Aug 2005 22:08:34 +0200
Lines: 27
Message-ID: <det5jd$ian$1@sea.gmane.org>
References:  <0B9EBBE7CA79D7118FD00002B3B2B9B910ECD62D AT nm75ex51 DOT das DOT honeywell DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; 	charset="iso-8859-2"
Content-Transfer-Encoding:  7bit
X-IsSubscribed: yes

Baksik, Frederick (NM75) wrote:

> The command /usr/bin/perlcc is actually a perl script that performs
the -r
> check to test if it can open the file.

Thanks for explanation. I assumed that perlcc is a binary file. IIRC this
is a known issue with perl scripts.

> So when perl does the -r check, it is correct based on the POSIX
permissions
> because your UID is not the same as the Administrators UID you should
not be
> able to open the file.  But when any program actually attempts to open
the
> file windows ( or is it cygwin ) will let it be opened.

Strange that bash works in a different manner:

$ [ -r foo.pl ] && echo ok
ok

$ perl -e '-r "foo.pl" and print "ok" or print "failed"'
failed

Krzysztof Duleba



--
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/