On 07/11/2012 11:02 AM, Darren J Moffat wrote: > On 07/11/12 00:56, Sašo Kiselkov wrote: >> * SHA-512: simplest to implement (since the code is already in the >> kernel) and provides a modest performance boost of around 60%. > > FIPS 180-4 introduces SHA-512/t support and explicitly SHA-512/256. > > http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf > > Note this is NOT a simple truncation of SHA-512 since when using > SHA-512/t the initial value H(0) is different.
Yes, I know that. In my original post I was only trying to probe the landscape for whether there is interest in this in the community. Of course for the implementation I'd go with the standardized truncation function. Skein-512 already includes a truncation function. For Edon-R, I'd have to devise one (probably based around SHA-512/256 or Skein). > See sections 5.3.6.2 and 6.7. > > I recommend the checksum value for this be > checksum=sha512/256 > > A / in the value doesn't cause any problems and it is the official NIST > name of that hash. > > With the internal enum being: ZIO_CHECKSUM_SHA512_256 > > CR 7020616 already exists for adding this in Oracle Solaris. Okay, if I'll implement it identically in Illumos then. However, given that I plan to use featureflags to advertise the feature to the outside world, I doubt interoperability will be possible (even though the on-disk format could be identical). Cheers, -- Saso _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
