Re: [PATCH] Remove absolute paths from gpg.rc
* On 2007.03.15, in <20070316004027.GD4694@xxxxxxxxxxxxxxxxxxxxx>,
* "Paul Walker" <paul@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Personally, I would still argue that /usr/bin is far and away the most
> common. Most people are running with gnupg supplied by their distro, and
I don't know if I agree with that. There are still a lot of people
running things that aren't Linux or XyzBSD, and most of those don't ship
gpg, and they don't put "local" software in /usr/bin.
> those update /usr/. People using OS X are in a definite minority; in
> addition, if they're savvy enough to use fink/darwinports to get mutt, it's
> kind of more or less automatic for them to be able to change an example
> muttrc.
I wouldn't agree with that either.
I can think of two compromises:
* as Thomas Dickey suggested, detect gpg at compile time and insert
the correct path into the installed muttrc files;
* enforce a sane PATH within mutt. This could, perhaps should be
limited to stripping out relative paths.
Failing something like this, I'd say it's preferable to make things
portable than to make things... *cough* "secure".
--
-D. dgc@xxxxxxxxxxxx NSIT University of Chicago