Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF)

X-seq: zsh-workers 15121
From: Brian Harvell <harvell@xxxxxxx>
To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF)
Date: Wed, 27 Jun 2001 09:02:40 -0400 (EDT)
Cc: Andrej Borsenkow <Andrej.Borsenkow@xxxxxxxxxxxxxx>, <zsh-workers@xxxxxxxxxxxxxx>
In-reply-to: <1010627074605.ZM5083@xxxxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm

On Wed, 27 Jun 2001, Bart Schaefer wrote:

>
> I think the question should always be "Any real reason to change the
> current behavior?"  So far I think not.
>

You could make the security argument since it's like having '.' at the front
of your path. If there was some bug found that would let a user change the
inode data of a file but not overwrite the file they could remove execute bits
to something like ls and put their own somewhere else.

I know that's far fetched but it might be nice to make it an option if it's not
that difficult.

Brian

-- 

Brian Harvell                harvell@xxxxxxx             http://ToolBoy.com/
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc

References:
- Re: PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF)
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author