3 ms·
Why not recommend SHA384 which AFAIK is exactly a truncated SHA512 without the "name collision" with SHA256? Or SHA224 which is the same from SHA256?
by masklinn 9y ago
Why not recommend SHA384 which AFAIK is exactly a truncated SHA512 without the "name collision" with SHA256? Or SHA224 which is the same from SHA256?
- tptacek 9y agoTo maximize both performance and the number of truncated bits, which is the factor mitigating length extension.
- masklinn 9y ago> both performance Surely SHA384 is no slower than SHA512/256 since both need to compute a SHA512 hash before truncation? > and the number of truncated bits, which is the factor mitigating length extension. Is there really a meaningful difference in mitigation between truncating 25% and 50% of the original hash?