Re: Possible security bug - :: in PATH behaves as if it were "."

On Sun, 16 Oct 2005, Asten Rathbun wrote: Unfortunately I have a slack distro that doesn't include bashbug and was having issues getting it compiled right, so please accept this bug report... this confounded me for awhlie [snip] ---A description of the bug I noticed that I was able to run exe

Re: Possible security bug - :: in PATH behaves as if it were "."

Asten Rathbun wrote: > Hi, > > Just kept looking for info on this, and found an old post on > gnu.bash.bug regarding this, where you (Chet) replied saying that this > is how $PATH should work. Do you have anything mentioning why that > is the case? It seems like a big security risk, seeing as s

Re: Possible security bug - :: in PATH behaves as if it were "."

Hi, Just kept looking for info on this, and found an old post on gnu.bash.bug regarding this, where you (Chet) replied saying that this is how $PATH should work. Do you have anything mentioning why that is the case? It seems like a big security risk, seeing as scripts can insert things into the

Possible security bug - :: in PATH behaves as if it were "."

Hi, Unfortunately I have a slack distro that doesn't include bashbug and was having issues getting it compiled right, so please accept this bug report... this confounded me for awhlie The version number and release status of Bash [EMAIL PROTECTED]:/usr/local/www/bin# bash --version GNU bash

Re: sigsegv in rl_resize_terminal

Sam Steingold wrote: > Do I understand correctly that > > #if defined(HAVE_READLINE) && defined(RL_ISSTATE) && defined(RL_INITIALIZED) > if (RL_ISSTATE(RL_INITIALIZED)) > rl_resize_terminal(); > #endif > > is the right way to do that? That should be enough to get you started. Chet --