3 ms·
Interesting… Note that they also add sha256 specific instructions. Which is good, because sha1 should no longer be used for new application and existing applic
by Perseids 13y ago
Interesting…
Note that they also add sha256 specific instructions. Which is good, because sha1 should no longer be used for new application and existing application should definitely start looking into an update path. See [1] for a rough estimate how fast the existing (publicly known) attacks become feasible.
I hope they are also working on implementing the sha3 permutation. That would allow for some really cool features to be super fast and simple like authenticated encryption or reseedable pseudo random number generation[2].
[1] https://www.schneier.com/blog/archives/2012/10/when_will_we_se.html https://www.schneier.com/blog/archives/2012/10/when_will_we_...
[2] For details see section 5 and 6 of https://eprint.iacr.org/2011/499.pdf https://eprint.iacr.org/2011/499.pdf