libsodium VS BLAKE3

Libsodium has been around for a while, so probably the reason it was posted is that version 1.0.19 was just released: https://github.com/jedisct1/libsodium/releases/tag/1.0.19-RE...

Updated NuGet and Swift packages are going to be uploaded soon.

AEGIS-128X and 256X are not there yet, but if you need them, they are available in libaegis: https://github.com/jedisct1/libaegis

All the code from libaegis will eventually be merged into libsodium, including the incremental update API which is especially useful for TLS.

To version the dependency you can check the current stable tree in git and save the date and git hash.

To address both of these vulnerabilities, you should instead use a library that handles these sharp edges for you. A well received library in the security and cryptography communities is libsodium. It has high level functions that handle password hashing and data encryption for you, reducing the risk that you introduce vulnerabilities in your code, such as you have here.

In general, cryptography is really hard. So for example, an attacker could construct a message that if you signed would leak information, ie it reduces the space of possible keys such that it can be brute forced. I’m not entirely sure if you could do that with a transfer function. But it’s certainly possible. That said, there are a ton of smart devs trying to prevent that as well so I’m not assuming anything here. But prudent practices are likely good to follow. Be very careful calling anything from your cold wallet etc. Use disposable keys for anything a bit risky. I took a sec to google an example and this is the closest I could find. https://github.com/jedisct1/libsodium/issues/170

Hi everyone! I'm learning Rust while on a break between jobs, and as I'm particularly interested in interfacing Rust with C and in cryptography, I've decided to write a wrapper around libsodium (https://github.com/jedisct1/libsodium) in Rust. This is purely a hobby project and I probably won't ever release it as there are already some open-source Rust bindings available for the library.

Can anyone recommend between Librandombytes and libsodium ramdombytes?

https://github.com/jedisct1/libsodium/tree/master/src/libsod...

> might be easier with a public domain license instead of the current ones

There reference implementation is public domain (CC0) or at your choice Apache 2.0

https://github.com/BLAKE3-team/BLAKE3/blob/master/LICENSE

Fyi, blake3 was released in 2019 and should probably be used over blake2 unless you have some strong reason not to. It's basically a reimplementation of blake2 with performance tweaks.

https://github.com/BLAKE3-team/BLAKE3

Many people will argue that today's compilers are so smart/optimized that you'd be a fool to try to outsmart the compiler with asm. I'm not 1 of them, but I know some. IMO it's all a bunch of bullshit, there's a goddamn reason all the cryptocurrency mining CPU/GPU code is all hand-written asm. there's a reason blake3 is written in asm ( https://github.com/BLAKE3-team/BLAKE3/blob/master/c/blake3_sse41_x86-64_windows_msvc.asm ) - but the thing is, 99.99% of the time, life is too short to outsmart the compiler (unless you're Alexander Yee)

I have been trying to optimize my code to create a fast hashing function to create and check b3 file integrity but b3sum is way way faster than my aproach, i have been trying to modify my code acordingly to https://github.com/BLAKE3-team/BLAKE3/blob/master/b3sum/src/main.rs with no luck, so if anyone can give me some tips/clues on how to achieve better speeds it would be incredible. Thx!!

BLAKE3 might be faster than KangarooTwelve and is also an XOF. It doesn't have the benefit of getting a working RFC draft proposal however.

You're saying the hash speed is 133 kB/s? That's extremely slow, for example BLAKE3 achieves 6.8 GB/s which is over 50000 times faster. Nobody wants to use such a slow hash function.

Try this one if you want a smaller, and particularly interesting crate: https://github.com/BLAKE3-team/BLAKE3

blake3 is a cryptographic hashing function, which is used during plotting's "forward propagation" step

BLAKE3 claims to be faster and more secure than both MD5 and SHA1.

More information: https://github.com/BLAKE3-team/BLAKE3