[openssl.org #1996] Probably a type conflict (BLOCK) in upcoming 1.0 version

2009-07-27 Thread Jens Rehsack via RT
Hi all, NetBSD5 (development version) is currently distributed with 'OpenSSL 1.1.0-dev 10 Jul 2009', which breaks compatibility with perl (detected when updating Crypt::SSLeay): /usr/pkg/bin/perl /usr/pkg/lib/perl5/vendor_perl/5.10.0/ExtUtils/xsubpp -typemap

[openssl.org #1997] [PATCH] DTLS timeout handling bug

2009-07-27 Thread Robin Seggelmann via RT
This patch fixes the timeout handling. The method dtls1_get_timeout() was intended to determine the next handshake message timeout when using select() calls, to set their timeout. This method is renamed to DTLSv1_get_timeout(), to fit the common naming scheme and the declaration is moved.

[openssl.org #1996] Probably a type conflict (BLOCK) in upcoming 1.0 version

2009-07-27 Thread Stephen Henson via RT
[rehs...@googlemail.com - Mon Jul 27 09:24:08 2009]: I checked both files, both declare BLOCK as (different) type. Perl5 declare this even in 5.8 (I didn't check earlier versions), but OpenSSL is not using it in 0.9.8. Maybe you should choose a different name for the memory block type

[openssl.org #1987] Definition of STRING conflicts with ntsecapi.h

2009-07-27 Thread Stephen Henson via RT
[c...@savagexi.com - Mon Jul 20 11:01:32 2009]: I assume other programs that use openssl and ntsecapi will also fail to compile. Any chance these generic typedefs can be changed to something like OPENSSL_STRING and OPENSSL_CSTRING? This has been changed to OPENSSL_STRING etc. Please

[PATCH] SHA512 ROTR macro fix for PowerPC using LP32 model

2009-07-27 Thread Ben Nason
Hi, I am new to the list, so apologies if I fail to follow any of the ground rules. I just ran into a bug where SHA384/512 were not being calculated correctly on the Cell processor. I tracked it down to the definition of the ROTR macro, which is assuming a 64 bit long, but in this case the

Re: [PATCH] SHA512 ROTR macro fix for PowerPC using LP32 model

2009-07-27 Thread Kyle Hamilton
Don't worry 'bout it too much. Could you please create that as a .diff file and attach it to an email to r...@openssl.org? The rt system creates a case that can be tracked. -Kyle H On Mon, Jul 27, 2009 at 3:26 PM, Ben Nasonbna...@netflix.com wrote: Hi, I am new to the list, so apologies if