On Thu, May 16, 2019 at 11:16:38AM +0300, Nikolay Borisov wrote: > It is labelled non-cryptographic, and is not meant to avoid intentional > collisions (same digest for 2 different messages), or to prevent > producing a message with predefined digest. > > This doesn't disqualify it, however we need to be aware its limitations. > Perhahps it could be used as a replacement for crc32c but definitely not > as secure crypto hash.
Agreed, but David's plan was to have 3 hashes and xx seems like a good fit for the 3rd fast, stronger than crc32c but not cryptographically secure option. I'll be looking into it for v3. -- Johannes Thumshirn SUSE Labs Filesystems [email protected] +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
