[Enigmail] [Fwd: GPG and Enigmail]

[Olav Seyfarth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Florian,

I'm German, too, but stick to eglish since your english is well and this list
is english. That way, other users may search for solutions to their problems
in the list archive. You should only directly contact team members if they ask
you to (e.g. to forward a problematic email message to analyse).

> I had installed Enigmail into SeaMonkey.
> I'm already using GnuPG 1.4.7. (with Win2k)

... which both aren't current versions. Since there is no more security support
on W2K, I suggest you switch to a still-supported version or a free OS ;-)
GnuPG 1.4.8 supports up to Vista (an all flavors of Linux, *BSD, ... of course.
GnuPG 2.0.8 now also officially supports Windows, but if you don't need its
X.509 features (which you most probably don't need), then stick with 1.4.8.
Also make sure that you use a current SeaMonkey, there have been security bugs.

> I've got the following Problem:
> Signing and Encryption does work perfectly.

If Signing does work, gnupg works fine, your secret keys are accessible, your
passphrase settings are correct, your passphrase is valid and message and
passphrase are transmitted correctly from Enigmail to GnuPG. 100% OK.

> when I want to decrypt or verfy some Messages, there is no output.

Can you decrypt from the command line? If the message in question is an INLINE
(as opposed to PGP/MIME) encrypted (i.e. you see a BEGIN PGP ENCRYPTED PART,
and a lot of Base64-encoded lines after), then save the whole email message
(e.g. by pressing Strg-S) as file "enc.eml". Then, from cmd.exe, cd to the
direcotry you saved the file to and exec "K:\Programme\GNU\GnuPG\gpg -d enc.eml"
to see whether it's a problem with Enigmail or GnuPG. If the message can be
decrypted from the command line, then there's something wrong with parameter
transfer (see below).

> What could be my Problem? In October 2007 it has worked very properly.

Signing still does work today?

> This output I get, by clicking onto "Decrypt/Verify":
> gpg command line and output:
> "K:\\Programme\\GNU\\GnuPG\\gpg.exe --charset utf8  --batch --no-tty
> --status-fd 2 --keyserver-options auto-key-retrieve --keyserver
> pool.sks-keyservers.net, subkeys.pgp.net, pgp.mit.edu,
> ldap://certserver.pgp.com -d --passphrase-fd 0 --no-use-agent
> Aufruf: gpg [Optionen] [Dateiname]"

The last line is the standard GnuPG message to indicate that the call syntax
was wrong, most probably arguments missing. But Enigmail called GnuPG with
proper arguments as you cited above. So either _K:_ is wrong (unprobable) or
K:\Programme\GNU\GnuPG\gpg.exe isn't really the GnuPG executable itself. We
had some issues with GPG4Win of that kind - they install a gpg.exe stub that
itself calls the real binary in .\bin, so if you have changed something with
your GnuPG installation, this might be an explanation. However, this error
should no longer happen with recent versions of all programs concerned (SM,
EM, GPG4Win). The file size of the stub is less than 100kB, the real gpg.exe
is more than 800kB. Also make sure that you always only have ONE gpg.exe on
your system, especially if you have PATH set to let the system find it.

Olav
- --
auch Alumni der Hochschule für Technik in Karlsruhe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iJwEAQECAAYFAkedhcAACgkQ/dJ0ek5GOmr/eQP/ZSOy6Jhzis/nKDAab5qcQ6zZ
hJkObS9nVgmS2DK/9GPZxf7w5qyd6fQr+Ff5Wh4PyY13ZcfwOfQHuTkALWO4aTWD
Yosoc1QR/z+rWsDhiNXWBKj5RdyAq/bjS/o9GMA1ZHpPz48vgVJG7FDLhfaVzkJl
sykTc8idOl8BFpe9NCo=
=iJTW
-----END PGP SIGNATURE-----