Re: Pika buildfarm member failure on pgcrypto/test sha2

Hi,

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) :

** /home/pgbuildfarm/workdir/HEAD/pgsql.12374/contrib/pgcrypto/expected/sha2.out Tue Feb 23 13:14:03 2010
--- /home/pgbuildfarm/workdir/HEAD/pgsql.12374/contrib/pgcrypto/results/sha2.out Tue Feb 23 19:01:19 2010
***************
*** 65,100 ****
--- 65,106 ----

-- SHA384
SELECT encode(digest('', 'sha384'), 'hex');
+ WARNING: problem in alloc set ExprContext: detected write past chunk end in block 0x7d4b0000, chunk 0x7d4b0088
encode
--------------------------------------------------------------------------------------------------
38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b
(1 row)

SELECT encode(digest('a', 'sha384'), 'hex');
+ WARNING: problem in alloc set ExprContext: detected write past chunk end in block 0x7d4b0000, chunk 0x7d4b0088
encode
--------------------------------------------------------------------------------------------------
54a59b9f22b0b80880d8427e548b7c23abd873486e1f035dce9cd697e85175033caa88e6d57bc35efae0b5afd3145f31
(1 row)

SELECT encode(digest('abc', 'sha384'), 'hex');
+ WARNING: problem in alloc set ExprContext: detected write past chunk end in block 0x7d4b0000, chunk 0x7d4b0088
encode
--------------------------------------------------------------------------------------------------
cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7
(1 row)

SELECT encode(digest('abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq', 'sha384'), 'hex');
+ WARNING: problem in alloc set ExprContext: detected write past chunk end in block 0x7d4b0000, chunk 0x7d4b0088
encode
--------------------------------------------------------------------------------------------------
3391fdddfc8dc7393707a65b1b4709397cf8b1d162af05abfe8f450de5f36bc6b0455a8520bc4e6f5fe95b1fe3c8452b
(1 row)

SELECT encode(digest('abcdefghbcdefghicdefghijdefghijkefghijklfghijklmghijklmnhijklmnoijklmnopjklmnopqklmnopqrlmnopqrsmnopqrstnopqrstu', 'sha384'), 'hex');
+ WARNING: problem in alloc set ExprContext: detected write past chunk end in block 0x7d4b0000, chunk 0x7d4b0088
encode
--------------------------------------------------------------------------------------------------
09330c33f71147e83d192fc782cd1b4753111b173b3b05d22fa08086e3b0f712fcc7c71a557e2db966c3e9fa91746039
(1 row)

SELECT encode(digest('abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz', 'sha384'), 'hex');
+ WARNING: problem in alloc set ExprContext: detected write past chunk end in block 0x7d4b0000, chunk 0x7d4b0088
encode
--------------------------------------------------------------------------------------------------
3d208973ab3508dbbd7e2c2862ba290ad3010e4978c198dc4d8fd014e582823a89e16f9b2a7bbc1ac938e2d199e8bea4

Anything I should try ?

Regards,

Rémi Zara

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.

--
marko

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.
Should I report a bug to NetBSD (and if so which one) ? Is there a workaround ?

Regards,

Rémi Zara

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