From: Brian Harvell <harvell@aol.net>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>,
<zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF)
Date: Wed, 27 Jun 2001 09:02:40 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.33.0106270859030.5675-100000@boondoggle.office.aol.com> (raw)
In-Reply-To: <1010627074605.ZM5083@candle.brasslantern.com>
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@aol.net http://ToolBoy.com/
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2001-06-27 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1000304181244.ZM24879@candle.brasslantern.com>
2001-06-21 21:46 ` status codes on Dec OSF Brian Harvell
2001-06-22 6:01 ` Andrej Borsenkow
2001-06-23 3:49 ` PATCH: POSIX exit codes (not quite Re: status codes on Dec OSF) Bart Schaefer
2001-06-23 18:22 ` Bart Schaefer
2001-06-25 5:57 ` Andrej Borsenkow
2001-06-27 7:15 ` Andrej Borsenkow
2001-06-27 7:46 ` Bart Schaefer
2001-06-27 13:02 ` Brian Harvell [this message]
2001-06-22 7:03 ` status codes on Dec OSF Sven Wischnowsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.33.0106270859030.5675-100000@boondoggle.office.aol.com \
--to=harvell@aol.net \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).