search for: skein

...50 AM, Chandler Carruth <chandlerc at google.com> > wrote: > > >> >>> What are the SHA-3 variants that you think would suite these needs ? >> >> > I want to look at the implementation complexity. The winner (and the > official SHA3 algorithm), BMW and Skein are all worth looking at. > > > If your primary criterion is through-put on large, desktop-class CPUs, > Skein is likely to be the winner. Keccak (the official SHA3) is also > pretty fast on CPUs (and significantly better in hardware implementations, > not that it matters here),...

...to burn space in order to *not* compare them at all. I would suggest storing 256 bits at least. > > >> What are the SHA-3 variants that you think would suite these needs ? > > I want to look at the implementation complexity. The winner (and the official SHA3 algorithm), BMW and Skein are all worth looking at. > >> >> Thanks >> >> Shankar Easwaran >> >> -- >> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted >> by the Linux Foundation >> >> > -------------- next part -------------- An HTM...

On May 8, 2013, at 10:50 AM, Chandler Carruth <chandlerc at google.com> wrote: > > What are the SHA-3 variants that you think would suite these needs ? > > I want to look at the implementation complexity. The winner (and the official SHA3 algorithm), BMW and Skein are all worth looking at. If your primary criterion is through-put on large, desktop-class CPUs, Skein is likely to be the winner. Keccak (the official SHA3) is also pretty fast on CPUs (and significantly better in hardware implementations, not that it matters here), and has the advantage of havi...

On Wed, May 8, 2013 at 10:29 AM, Shankar Easwaran <shankare at codeaurora.org>wrote: > On 5/8/2013 11:35 AM, Chandler Carruth wrote: > >> Interestingly newer, supposedly "more secure" digest algorithms are also >> very often significantly faster. I don't think we want any of the ones >> mentioned here, I think we want one of the candidates is the SHA3

On 5/8/2013 11:35 AM, Chandler Carruth wrote: > Interestingly newer, supposedly "more secure" digest algorithms are > also very often significantly faster. I don't think we want any of the > ones mentioned here, I think we want one of the candidates is the SHA3 > competition which had truly stellar software implementation > throughput. I'm hoping to add support

We still have MD5 as our default password hash, even though known-hash attacks against MD5 are relatively easy these days. We've supported SHA256 and SHA512 for many years now, so how about making SHA512 the default instead of MD5, like on most Linux distributions? Index: etc/login.conf =================================================================== --- etc/login.conf (revision

...recompression, and its RAM usage was further reduced. * The largest size of indirect block possible has been increased from 16KB to 128KB, and speculative prefetching of indirect blocks is now performed. * Improved ordering of space allocation. * The SHA-512t256 and Skein hashing algorithms are now supported. __________________________________________________________________ Kernel evdev Support Links evdev WIP Repository URL: https://github.com/wulf7/FreeBSD Original evdev Proposal URL: https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchs...

...recompression, and its RAM usage was further reduced. * The largest size of indirect block possible has been increased from 16KB to 128KB, and speculative prefetching of indirect blocks is now performed. * Improved ordering of space allocation. * The SHA-512t256 and Skein hashing algorithms are now supported. __________________________________________________________________ Kernel evdev Support Links evdev WIP Repository URL: https://github.com/wulf7/FreeBSD Original evdev Proposal URL: https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchs...