On Sat, Jun 06, 2009 at 02:40:04PM +1000, Russell Coker wrote: > Package: libssl0.9.8 > Version: 0.9.8g-15+lenny1 > Severity: normal > > Here are some valgrind warnings. It would be good if these could be fixed > even > if they happen to be harmless so that they don't get in the way of debugging > applications that use libdkim and libssl. > > ==12015== Conditional jump or move depends on uninitialised value(s) > ==12015== at 0x428EA37: BN_mod_inverse (bn_gcd.c:215) > ==12015== by 0x4292920: BN_MONT_CTX_set (bn_mont.c:406) > ==12015== by 0x4292C67: BN_MONT_CTX_set_locked (bn_mont.c:476) > ==12015== by 0x42A89DA: RSA_eay_public_decrypt (rsa_eay.c:672) > ==12015== by 0x42A998D: RSA_public_decrypt (rsa_lib.c:300) > ==12015== by 0x42AA7DC: RSA_verify (rsa_sign.c:174) > ==12015== by 0x42D23C6: EVP_VerifyFinal (p_verify.c:98) > ==12015== by 0x4035AE8: (within /usr/lib/libdkim.so.0d.1) > ==12015== by 0x402D01D: DKIMVerifyResults (in /usr/lib/libdkim.so.0d.1) > ==12015== by 0x804A59C: (within /usr/sbin/truedomain_cmilter) > ==12015== by 0x804D3F9: (within /usr/sbin/truedomain_cmilter) > ==12015== by 0x439A33E: (within /usr/lib/libmilter.so.1.0.1) > > ==12015== Conditional jump or move depends on uninitialised value(s) > ==12015== at 0x4285491: BN_div (bn_div.c:190) > ==12015== by 0x428B571: BN_nnmod (bn_mod.c:132) > ==12015== by 0x428F34A: BN_mod_inverse (bn_gcd.c:486) > ==12015== by 0x4292920: BN_MONT_CTX_set (bn_mont.c:406) > ==12015== by 0x4292C67: BN_MONT_CTX_set_locked (bn_mont.c:476) > ==12015== by 0x42A89DA: RSA_eay_public_decrypt (rsa_eay.c:672) > ==12015== by 0x42A998D: RSA_public_decrypt (rsa_lib.c:300) > ==12015== by 0x42AA7DC: RSA_verify (rsa_sign.c:174) > ==12015== by 0x42D23C6: EVP_VerifyFinal (p_verify.c:98) > ==12015== by 0x4035AE8: (within /usr/lib/libdkim.so.0d.1) > ==12015== by 0x402D01D: DKIMVerifyResults (in /usr/lib/libdkim.so.0d.1) > ==12015== by 0x804A59C: (within /usr/sbin/truedomain_cmilter) > > These errors are repeatable on my system.
How do I reproduce them? Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
