On Tue, Jun 04, 2019 at 09:37:30AM +0200, Johannes Thumshirn wrote: > > Let me summarize the current satus: > > > > for strong hash we have SHA256 and BLAKE2. For the fast hash xxhash and > > murmur3 have been suggested. Let me add XXH3 and xxh128 for now (they're > > not finalized yet). > > I know there's a tendency to not trust FIPS but please let's not completely > rule out FIPS approved algorithms (be it SHA-2 or SHA-3) because we will get > asked to include one sooner or later.
That's not about FIPS, but the practical reasons. If it's slow nobody will use it. For example, if a crypto-strong hash is used as a hint for deduplication, this means we'll have to count with it for the additional structures that do the reverse mapping from checksum -> block.
