On Thu, 7 May 2009 17:39, ste...@syslang.net said: > /home/steveo/libexec/ppf/ppf_verify: pgp command failed"
I don't know this tool. > gpg: Signature made Thu May 7 02:19:07 2009 EDT using RSA key ID EF733C40 > gpg: BAD signature from "Javier Fern I just did a verify: $ gpg --verify -v x gpg: armor header: Hash: SHA256 gpg: armor header: Version: GnuPG v1.4.9 (MingW32) gpg: armor header: Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org [..] gpg: Good signature from "Javier fern.%g�...@dez Almirall (aka Faramir.cl)" [...] gpg: textmode signature, digest algorithm SHA256 and it works fine. Maybe the tool can't cope with the base64 encoded clearsigned message: > The message looked like this: > Content-Transfer-Encoding: base64 [..] > LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEEyNTYKCmdwZzIuMjAu > bWFuaWFtc0BkZmdoLm5ldCBlc2NyaWJpw7M6Cj4gRGVhciBMaXN0Cj4gCj4gCj4gSG93IHRvIGlt You need to do something like mimencode -u | gpg --verify However the mail reader usually does this for you. Shalom-Salam, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
