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
Message-ID: <4311D541.BEEB9FFE@dessent.net>
Date: Sun, 28 Aug 2005 08:16:17 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: perlcc and permissions
References: <desi8j$un6$1 AT sea DOT gmane DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Krzysztof Duleba wrote:

> $ ls -l foo.pl
> -rwx------+ 1 Administratorzy Brak 34 Aug 28 16:29 foo.pl
> 
> I guess that in strict mode the file should not be readable by me.
> However, cat and perl can read it without problems.

I don't know why perlcc complains when perl does not.  But the above
statement is not necessarily true.  The "+" in the last column of the
permissions means that there are extended ACLs that cannot be mapped to
the simple posix "rwx" scheme.  So you may very well have read and/or
write access to the file, but programs that only know about posix
permissions have no way of knowing this.  You need to use a tool such as
getfacl, cacls, or xcacls to see the full ACLs of the file.

Brian

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