Gpgverify assumes wrong default gnupg setup (with patch)
Heath Kehoe
hakehoe at avalon.net
Sat Feb 28 17:22:02 UTC 2004
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I disagree. The manual page for pgpverify says: "By default, when
running as part of INN, pgpverify expects the PGP key ring to be
found in pathetc/pgp".
After importing the PGP keys, I moved the pubring file to
<pathetc>/pgp/, and gpgverify works without needing modification.
The comment in the code is what needs to be changed, IMHO. It
should read:
# The keyring by default is stored in <newsetc>/pgp
# If elsewhere, set appropriately the next line
- -Heath
On Feb 28, 2004, at 6:08, Toon van der Pas wrote:
> Hi,
>
> I'm running inn-STABLE-20040118.
> The way gpgverify is programmed, everybody will have to edit it
> in order to get it working, even when the gnupg setup is completely
> standard. However, a comment line in gpgverify suggests that it was
> meant to function out-of-the-box in case of a standard gnupg setup.
> Here is that comment:
>
[...]
> # if you keep your keyring somewhere that is not the default used by
> gpg,
> # set appropriately the next line.
> -my $keyring = ($inn::newsetc ? $inn::newsetc . '/pgp/' : '') .
> 'pubring.gpg';
> +my $keyring = ($inn::newshome ? $inn::newshome . '/.gnupg/' : '') .
> 'pubring.gpg';
>
> # If you have INN and the script is able to successfully include your
> # innshellvars.pl file, the value of the next two variables will be
>
> --
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFAQM5P4uXPAG0A1J4RAlNnAJ0UPwSPLF9GpPul10vox6CpPVeZwQCeKZ3K
J1FFpoEh76WuYEOBb4M7foI=
=jFRk
-----END PGP SIGNATURE-----
More information about the inn-workers
mailing list