Mailing List Archive

Ken,
Be sure that both users are using the same version of GPG. Versions
prior to 1.0.2 had a problem with encoding signatures. You'll see failure
if sending messages between incompatible versions. See
the --emulade-md-encode-bug option in 1.0.2.

Scott F. Crosby
E-Mail : skroz@skroz.net
Web : http://hcgl.eng.ohio-state.edu/~crosbys

"Science is like sex: sometimes something useful comes out, but that is
not the reason we are doing it" -- Richard Feynman

I can accept encrypted messages enciphered with Verisign or GPG/PGP. Both
public keys can be found below or at
http://hcgl.eng.ohio-state.edu/~crosbys

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org

mQGiBDmPm5ERBACnEMaMdpB8fEQaOBmzsJtn2fPKRy6si7140x2sevGeBC2GHsFS
qaKCUgyglofaf2sIlPXdqPxjfc8R24e5vQ5qlSyUi0QJdlOWrygQ6NJGAX0ptNRr
wv29QHjrsXvbLndBmkaeyqpLzionA0HkYm79eKSsHf6ob6Svrg3BODep7wCg7lK/
05HNSo5cQvsy4dKUAmhnwg0D/1pmi2dQyYj8UQhaUeX9FzeGiNzXkTZTQWt2hEU0
s2Vgv9hkMC9wseJmKrr5tX+M7J0ArWyxWQqEwWTxKHVkIyTI1+ls3GmUWhB0eQ65
bsR5ttwcYKMFFq+ReigKzBBc/8SxnwHkjMg+0IRpmfH5E7aN4yT8Dytq65naI2OB
oK9bBACE/i8yKjIuJ3hf8xm/47TuogUug2jX5N1d1z5IBTYxr7m8qSuFy8haRkar
ZlWExbTdaADGUtukOWWLhGHXCXNZU/0jjzLMlLn066NijOruI7V3vCKRT/StfFl5
bsu2GmnOly8LqlRmJUVhUHmQBXZ1plO0Rtry9RE9Hrtd0nmMnbQwU2NvdHQgRi4g
Q3Jvc2J5IChTdGFuZGFyZCBLZXkpIDxza3JvekBza3Jvei5uZXQ+iFwEExECABwF
AjmPm5EFCQHhM4AECwoEAwMVAwIDFgIBAheAAAoJEKTwLT3Yvg4t374AoLzp7x0T
GPUWnhemIW9Ivqxg4CdkAKCA+x0dM+dKDdOM1kpO/MVkZJ0UirkBDQQ5j5uwEAQA
8nWAG53Bh9DBWnbI2Oeg7F+BlzIPf+HcxGAfAjHpqK0cYktOzqjeJo2B75eY9t5g
L8T1p9tk089yTa6u2oSHoGxSNW/HbOgnndJTodCoxP41waINr66r7COWMOYNmSRW
Bt6C2yaHYWNjNuUGWiSe5XPWPYceIri8by/jTy+eaXcABRMEALv2+/j6yiHsxJJh
16za285Zv7kyMdRB1ClIK/GLIP4mMjNBUxsNIRntIhaON4ONucVRM6nb2Y4iA5Eg
prFrhziZB+UPBuipSeTLJaM2wXTPdBFMsAibuF2Tv1EbampIqR9wYOfYiKQetHXX
JSqg8cS+z6bLqx94enyfr9Su3j3xiEwEGBECAAwFAjmPm7AFCQHhM4AACgkQpPAt
Pdi+Di0W6ACgxLO1S4jNayJgm++dchfIBSzCC2QAoKw/28CyxAu1eUUleiG49Ae0
Zp1m
=zxK6
-----END PGP PUBLIC KEY BLOCK-----




-----Original Message-----
From: kenschar@pisenegal.com [mailto:kenschar@pisenegal.com]On Behalf Of
Ken Schar
Sent: Thursday, August 10, 2000 6:14 AM
To: GNU Privacy Guard Users
Subject: Signature fails


Hi there,

I am using pine with gpg4pine to encrypt/decrypt and I am using
GPG 1.02

Encryptiong & decryption are working fine however, when I send out and
encrypted/signed message the signature is always invalid on the receivers
computer.

Any ideas what to check?? Everything encrypts fine just no signature.

Thanks for any suggestions/help!
Ken




--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org

On Thu, 10 Aug 2000, Scott F. Crosby wrote:

> Be sure that both users are using the same version of GPG. Versions
> prior to 1.0.2 had a problem with encoding signatures. You'll see failure
> if sending messages between incompatible versions. See
> the --emulade-md-encode-bug option in 1.0.2.

However, this happens only in cases where a non-sstandard key was
used. Quite a long time ago, GnuPG changed it's default behaviour to
create DSS (meaning DSA + SHA1) signatures and not anymore a signature
based on DSA + RIPE-MD160. This option comes handy when you use an
Elgamal encryption+signing key, which is something I don't suggest
anymore.

I did some benchmarks and at least on a Mobile Pentium 300 SHA-1 is a
little bit faster than RIPE-MD160.

Werner

--
Werner Koch GnuPG key: 621CC013
OpenIT GmbH http://www.OpenIT.de

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org