|
Anonymous »
2022-08-06 03:17:29
BLAKE3 is, let be honest, a cut off BLAKE2, less secure (Still secure enough, though). BLAKE3 and XXH are the fastest secure checksum hashes. But, BLAKE2 is widespread, more secure, and is present on all Linux systems, so I think it must be added 1st. All the others are not a part of Coreutils.
On speed, BLAKE3 and XXH are equally fast, it all bottlenecks into the drive's speed, and I have an NVMe SSD, still doesn't outperform each other. Then, from less collision standpoint, may I propose SKEIN-1024-1024? 1024-bit! The only 1024-bit hash that has passed most rounds of the SHA3 competition. Additionally, as Perl C modules on Github by Gray, other hashes exist: BLAKE1, ECHO, GROESTL, JH, SKEIN. Isn't a little strange we don't have the 1st most secure BLAKE? Non-cryptographic fuzzy hashes can be useful for knowing how similar a file is: SSDEEP, TLSH. For the future, in case SHA is broken, SHA3 is never a bad idea to add. Anyway, this is probably overkill, stick with BLAKE2 for Osiris' and wider compatibility's sake.
In short, BLAKE2, the B variant, is default on Linux and is present everywhere including RHash for Windows, unlike BLAKE3. Therefore BLAKE2b should be added before BLAKE3.
|
|
Back to: Nintendo - Nintendo 3DS
Add BLAKE2 to checksum