Re: stuff in ~/bin won't run
Dotan Cohen wrote:
> 2009/1/13 Steve Kemp <skx@debian.org>:
> > On Tue Jan 13, 2009 at 21:08:02 +0200, Dotan Cohen wrote:
> >
> >> Why is that dangerous? Because if your account is compromised then
> >> critical system programs (ls, cd, and the like) can be easily replaced
> >> with compromised versions. Putting your own bin at the end of the path
> >> is meant to thwart this.
> >
> > If your account is compromised then why do you imagine your
> > settings will be untouched?
> >
>
> Exactly, this is the fallacy.
>
> > People typically put their ~/bin directory first, precisely
> > so that they can override system-wide commands.
> >
>
> Exactly.
Could you not just give your versions of the apps you want to run different
names? Would that not be safer? What I've done in the past is to add _mine to
end of the names, ie. 'todisc_mine'.
> > As for why it didn't work - the OP seemed to have said:
> >
> > PATH = ...
> >
> > (ie. Spaces around the equals sign. This will not work.)
> >
>
> I gave him an example of a valid .bash_profile file.
--
J
Reply to: