On Sat, Jun 28, 2014 at 12:28:45AM +0200, Stephan M?hlstrasser wrote:
> Maybe b is uninitialized?
I would expect function arguments to be initialized by virtual of
being passed to the function, and the use of uninitialized values
to be attributed to the caller. However, if valgrind does not
cons
Am 27.06.2014 18:10, schrieb Viktor Dukhovni:
On Fri, Jun 27, 2014 at 05:29:52PM +0200, Stephan M?hlstrasser wrote:
==14780== Use of uninitialised value of size 8
==14780==at 0x72378B: bn_GF2m_mul_1x1 (bn_gf2m.c:179)
What is the commit id of the openssl version you're buil
Hi,
I have an implementation of a multi-threaded HTTP server that I wrote using
OpenSSL version 1.0.1g. Currently, on initialization of the server, I load my
private key from disk and store it in an EVP_PKEY pointer. Whenever I accept a
new connection, I use that same pointer to an EVP_PKEY in
On Fri, Jun 27, 2014 at 05:29:52PM +0200, Stephan M?hlstrasser wrote:
> ==14780== Use of uninitialised value of size 8
> ==14780==at 0x72378B: bn_GF2m_mul_1x1 (bn_gf2m.c:179)
What is the commit id of the openssl version you're building?
What is on line 179 of that file. I have:
Hi,
after switching to a current build from the OpenSSL_1_0_2-stable branch
on a Linux 64-bit system I'm getting the below valgrind reports about
use of uninitialised values when creating ECDSA signatures. This is a
build created with -DPURIFY.
Those didn't happen with OpenSSL 1.0.0c. I only
On 2014-06-25 at 22:22, Michael Wojcik wrote:
[…]
>> But if two or more parallel SSL connections
>> are initiated you would AFAICS require a unique index variable per running
>> SSL*.
>
> No, that's not how it works. You need one index value per item to be stored
> in a given SSL object. You ha
