The following commit fixes an type checking/casting issue in the
SKM_ASN1_SET_OF_i2d macro
http://cvs.openssl.org/filediff?f=openssl/crypto/stack/safestack.hv1=1.72.2.5v2=1.72.2.6
However, the SKM_ASN1_SET_OF_d2i needs a similar fix too:
$ diff -u openssl/safestack.h.orig openssl/safestack.h
The only reference I can find to OPENSSL_NO_RAND is in
crypto/dh/dh_key.c and it shouldn't really be in there. There isn't an
option to compile OpenSSL without a PRNG as just about everything uses it.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now
[claes.west...@tieto.com - Thu May 06 17:32:44 2010]:
Hello!
I am trying to create a S/MIME document that is sent as a base64 coded
data element to a web service. When the server side decodes the base64
and then tries to verify the document they get an error message.
faultstring=invalid
On Wed, 2010-05-26 at 21:32 +0200, Ger Hobbelt wrote:
Those [i_a] bits are my markers in our local code base so I know which edits
are mine when doing a (manual) merge with 'vanilla' CVS HEAD. Yes, I know
there are smarter systems around, but I've been 'tracking' OpenSSL for
almost a decade
David Woodhouse wrote:
On Wed, 2010-05-26 at 21:32 +0200, Ger Hobbelt wrote:
Those [i_a] bits are my markers in our local code base so I know which edits
are mine when doing a (manual) merge with 'vanilla' CVS HEAD. Yes, I know
there are smarter systems around, but I've been 'tracking'
On Thu, 2010-05-27 at 17:51 +0200, Lutz Jaenicke wrote:
David Woodhouse wrote:
On Wed, 2010-05-26 at 21:32 +0200, Ger Hobbelt wrote:
Those [i_a] bits are my markers in our local code base so I know which
edits
are mine when doing a (manual) merge with 'vanilla' CVS HEAD. Yes, I know
