From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] bash wizardry needed: PATH and MANPATH grow and grow and grow
Date: Fri, 26 May 2006 19:52:17 -0700 [thread overview]
Message-ID: <9acccfe50605261952o7b548a6ah9710d3f8fff42f0d@mail.gmail.com> (raw)
In-Reply-To: <169ffc030605251827p1d046645oaf1cd85ede10c6e5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On 5/25/06, znx <znxster@gmail.com> wrote:
>
> > This _does_ help. It's mysterious enough that I tested it, and it seems
> to
> > work except that it removes "." from any path. This is not quite what I
> want.
>
> Glad it was almost a success ;) Interesting, thats not something I
> noticed before, I have never wished "." in my PATH, I should point out
> of course that "." in your PATH is a security risk waiting to happen
> ;)
Open to debate. I'd think it's not very dangerous at the *end* of the PATH.
The usual worry is a Trojan masquerading as a normal utility, chosen
early because of the order of things in the searchpath. When I use ".", I
put it at the end. It's no worse than the fairly common ~/bin in a
searchpath,
which I'd actually rate more dangerous --
1) It's just as hard/easy to put something in ~/bin as in ~/
2) It's more likely to go unnoticed in ~/bin
And, since I do lots of development of itsy-bitsy scripts and C programs,
I'm using such stuff all the time.
Nevertheless it should not be removing the entry unless its a dup. I
> have quickly confirmed the behaviour it is defn stripping all "."
> entries.
>
> *sigh* the script needs some work .. I'll play with it again tomorrow....
>
> Thanks for the feedback,
> Mark
Thanks...
++ kevin
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 1953 bytes --]
next prev parent reply other threads:[~2006-05-27 2:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 22:56 [gentoo-user] bash wizardry needed: PATH and MANPATH grow and grow and grow Kevin O'Gorman
2006-05-23 20:06 ` znx
2006-05-24 14:58 ` Kevin O'Gorman
2006-05-26 1:27 ` znx
2006-05-27 2:52 ` Kevin O'Gorman [this message]
2006-06-03 21:11 ` znx
2006-07-05 19:33 ` Boyd Stephen Smith Jr.
2006-07-07 18:31 ` Kevin O'Gorman
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=9acccfe50605261952o7b548a6ah9710d3f8fff42f0d@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox