Your message dated Sun, 24 Jul 2016 15:44:13 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-openssl-devel] Bug#532059: libssl0.9.8: valgrind 
reports: Conditional jump or move depends on uninitialised value(s)
has caused the Debian Bug report #532059,
regarding libssl0.9.8: valgrind reports: Conditional jump or move depends on 
uninitialised value(s)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
532059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532059
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash

Versions of packages libssl0.9.8 depends on:
ii  debconf [debconf-2.0]  1.5.24            Debian configuration management sy
ii  libc6                  2.7-18            GNU C Library: Shared libraries
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

libssl0.9.8 recommends no packages.

libssl0.9.8 suggests no packages.

-- debconf information:
  libssl0.9.8/restart-failed:
* libssl0.9.8/restart-services: ntp bind9 postfix ssh



--- End Message ---
--- Begin Message ---
Version: 1.0.1t-1+deb8u2

On 2009-06-14 15:39:11 [+1000], Russell Coker wrote:
> I have attached the source to a dkim test program which triggers the valgrind 
> error reports.  Run it with a single command-line parameter such as the 
> following:
> valgrind ./a.out test-msg.mbox
> 
> It will give the following errors:

I a closing this bug and marking it as fixed in the current stable version.
The upstream bug report is somehow marked as fixed (with no explicit commit)
and your testcase does not report any bugs on stable:

|$ valgrind ./dkim-test test-msg.mbox 
|==52903== Memcheck, a memory error detector
|==52903== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
|==52903== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
|==52903== Command: ./dkim-test test-msg.mbox
|==52903== 
|Result 0 is pass for domain dunno
|==52903== 
|==52903== HEAP SUMMARY:
|==52903==     in use at exit: 6,048 bytes in 9 blocks
|==52903==   total heap usage: 185 allocs, 176 frees, 16,796,115 bytes allocated
|==52903== 
|==52903== LEAK SUMMARY:
|==52903==    definitely lost: 9 bytes in 2 blocks
|==52903==    indirectly lost: 0 bytes in 0 blocks
|==52903==      possibly lost: 0 bytes in 0 blocks
|==52903==    still reachable: 6,039 bytes in 7 blocks
|==52903==         suppressed: 0 bytes in 0 blocks
|==52903== Rerun with --leak-check=full to see details of leaked memory
|==52903== 
|==52903== For counts of detected and suppressed errors, rerun with: -v
|==52903== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Sebastian

--- End Message ---

Reply via email to