From: | Marko Kreen <markokr(at)gmail(dot)com> |
---|---|
To: | Rémi Zara <remi_zara(at)mac(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Pika buildfarm member failure on pgcrypto/test sha2 |
Date: | 2010-02-24 17:11:21 |
Message-ID: | e51f66da1002240911g2445394q8534eeaf7464c5fc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/24/10, Rémi Zara <remi_zara(at)mac(dot)com> wrote:
> Le 24 févr. 2010 à 01:04, Marko Kreen a écrit :
> > On 2/24/10, Rémi Zara <remi_zara(at)mac(dot)com> wrote:
> >> Pika, which has been upgraded to NetBSD/mips 5.0.2, failed twice in a row pgcrypto/test sha2 because of the following warning (identical each time) :
> >>
> >
> >> Anything I should try ?
> >
> > Please try --without-openssl.
>
>
> Indeed, it works.
>
> My openssl version is OpenSSL 0.9.9-dev 09 May 2008 bundled with NetBSD 5.0.2.
I managed to reproduce it on 5.0.2/x86. The problem is their
openssl library - sha384 writes out 64 bytes instead of 48.
As both OpenSSL 0.9.8 and 1.0-beta5 are fine, it's a netbsd-only
problem. Their OpenSSL version is 0.9.9, which seems to be a
random CVS snapshot before 1.0-beta era. Seems they did not bother
to track fixes in openssl HEAD.
> Should I report a bug to NetBSD (and if so which one) ?
Yes - buggy sha384.
> Is there a workaround ?
Turn OpenSSL off...
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Rémi Zara | 2010-02-24 17:14:45 | Re: NaN/Inf fix for ECPG |
Previous Message | Rémi Zara | 2010-02-24 17:05:15 | Re: NaN/Inf fix for ECPG |