Skip Menu |

This queue is for tickets about the Digest-SHA3 CPAN distribution.

Report information
The Basics
Id: 110364
Status: rejected
Worked: 5 min
Priority: 0/
Queue: Digest-SHA3
People
Owner: Nobody in particular
Requestors: daath101 [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Tue Dec 15 16:16:04 2015 daath101 [...] gmail.com - Ticket created
Subject: Differences in output from sha3_512_base64 between 0.22 and 0.24
Date: Wed, 16 Dec 2015 08:15:41 +1100
To: bug-Digest-SHA3 [...] rt.cpan.org
From: Fletch <daath101 [...] gmail.com>
I've noticed that the sha3_512_base64 function is producing different output, between different versions of the module. On CentOS 7, perl-Digest-SHA3-0.24-1.el7.x86_64 (epel) $ perl -e 'use Digest::SHA3; print Digest::SHA3::sha3_512_base64("asd")."\n";' nmHxyCEMEg/NQTQ/0uuHNPyVPe4E7TGDDacBc82z5WG+e7ATiqzV0nejz+bLcZTxzrdSiwMn9Il51JkK0qy05Q On Debian 8, libdigest-sha3-perl 0.22-2 amd64 $ perl -e 'use Digest::SHA3; print Digest::SHA3::sha3_512_base64("asd")."\n";' P7Z8i1EtjOczJNsC3aLRnr+51qkjxI+1A74+DHx1LrhOTaCBhmUTOidjjc6OnoaWpRtktrJHNUdkYJ8itOZdNQ After removing the package on Debian 8, and installing 0.24 via cpan (Module = Digest::SHA3 (MSHELOR/Digest-SHA3-0.24.tar.gz)) $ perl -e 'use Digest::SHA3; print Digest::SHA3::sha3_512_base64("asd")."\n";' nmHxyCEMEg/NQTQ/0uuHNPyVPe4E7TGDDacBc82z5WG+e7ATiqzV0nejz+bLcZTxzrdSiwMn9Il51JkK0qy05Q I also tested the cpan 0.22 version on a clean install $ perl -e 'use Digest::SHA3; print Digest::SHA3::sha3_512_base64("asd")."\n";' P7Z8i1EtjOczJNsC3aLRnr+51qkjxI+1A74+DHx1LrhOTaCBhmUTOidjjc6OnoaWpRtktrJHNUdkYJ8itOZdNQ The change in output appears from 0.23 $ perl -e 'use Digest::SHA3; print Digest::SHA3::sha3_512_base64("asd")."\n";' nmHxyCEMEg/NQTQ/0uuHNPyVPe4E7TGDDacBc82z5WG+e7ATiqzV0nejz+bLcZTxzrdSiwMn9Il51JkK0qy05Q F
  Wed Dec 16 04:43:23 2015 mshelor [...] cpan.org - Correspondence added 5 min
Yes, the outputs are different. As of version 0.23 the Digest::SHA3 module reflects the then-recent updates made to FIPS 202 which called for the use of domain separation bits (ref. the Changes file). These updates caused changes to all digest outputs, as expected. To my knowledge the current Digest::SHA3 module passes all official, published test vectors, including those with partial-byte inputs. If you know of any exceptions, let me know. Mark
  Wed Dec 16 04:43:24 2015 The RT System itself - Status changed from 'new' to 'open'
  Wed Dec 16 04:43:24 2015 mshelor [...] cpan.org - Status changed from 'open' to 'rejected'
  Wed Dec 16 17:56:48 2015 daath101 [...] gmail.com - Correspondence added
Subject: Re: [rt.cpan.org #110364] Differences in output from sha3_512_base64 between 0.22 and 0.24
Date: Thu, 17 Dec 2015 09:56:31 +1100
To: bug-Digest-SHA3 [...] rt.cpan.org
From: Fletch <daath101 [...] gmail.com>
Thanks Mark. Was a little unsure which version I should trust moving forward with my project. Latest is the one. Cheers F On 16/12/2015 8:43 pm, Mark Shelor via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=110364 > > > Yes, the outputs are different. As of version 0.23 the Digest::SHA3 module reflects the then-recent updates made to FIPS 202 which called for the use of domain separation bits (ref. the Changes file). These updates caused changes to all digest outputs, as expected. > > To my knowledge the current Digest::SHA3 module passes all official, published test vectors, including those with partial-byte inputs. If you know of any exceptions, let me know. > > Mark >