3 ms·
JP Aumasson just announced Blake3 at Real World Crypto a few days ago during the lightning talks. This was also right after he presented on "Too Much Crypto"[1]
by baby 7y ago
JP Aumasson just announced Blake3 at Real World Crypto a few days ago during the lightning talks. This was also right after he presented on "Too Much Crypto"[1] which argues that we use too many rounds in symmetric constructions: our security margins are too high and don't match any of the best "practical" attacks. We're too paranoid for our own good. He suggests reducing the number of rounds for a number of constructions like AES, SHA-3, Blake2, etc.
[1]: https://eprint.iacr.org/2019/1492.pdf https://eprint.iacr.org/2019/1492.pdf
Blake3 is in part a reduction of number of rounds (so it's faster), it's also a bit of a design change (the round function, and the parallelization), and it's now just one multi-purpose function (instead of several instances) that takes an arbitrary-length input and gives an arbitrary-length output.
My questions are:
* what are standards using Blake2 (like Noise) going to do?
* what do cryptanalysts think?
* is it really that fast? (I'll have to benchmark this for my own use-case.)
- dathinab 7y ago> which argues that we use too many rounds in symmetric constructions: our security margins are too high and don't match any of the best "practical" attacks. We're too paranoid for our own good. He suggests reducing the number of rounds for a number of constructions like AES, SHA-3, Blake2, etc. This seems a quite dangerous way of thinking. New attacks, methods to attack crypto are discovered regularly. A view years ago people also said SHA-1 will never get broken to the degree it just got broken a recently. So the only think we can do is to be slightly paranoid, everything else would be strongly negligent. Especially if we consider how long it often takes in practice to update software and phase out previous encryption and hash methods without having to worry about e.g. downgrade attacks or similar. Sure software should be possible to be updated asap, but honestly how long will it take until SHA-1 is phased out? EDIT: Through that also means if you believe you will always be able update the _deployed_ relevant parts of your software ASAP (which can't work for libraries) and you are sure that you will follow the crypto community close enough and you believe some one else does so to if you are unavailable because of sickness, then yes go ahead and use less paranoid/secure crypto.
- bawolff 7y ago> This seems a quite dangerous way of thinking. New attacks, methods to attack crypto are discovered regularly. He does actually address this counterargument in his paper. In fact most of his paper is a rebuttal to this argument (the status quo wisdom, so to speak).
- ganzuul 7y agoAgreed. We are not just securing for today, we are securing for perhaps decades into the future. If we don't know for sure what the threat is, then the right measure of paranoia is as much as we can afford. We are not just securing ourselves, but our social network too. Something you do can be used to discredit your kids and grand-kids a long time from now.
- tylersmith 7y agoWhy not increase the rounds then? What makes the current security margins acceptable but not smaller margins?
- ganzuul 7y agoI don't know a reason for why they are acceptable. AES256 is considered quantum-proof, but there exists another theoretical quantum computer design which seems to raise the bar again. I don't know if there exists a theoretical limit for how powerful quantum computers can get.
- bawolff 7y agoWhat other theoretical quantum design? AES256 is considered quantum proof because grover's algorithm can in theory basically half they key size, and aes128 is secure on normal computers [we are still very very very very far away from a quantum computer that can use grover's algorithm to bruteforce aes128]. I'm not an expert on the subject but i believe a new quantum algorithm that could break aes256 would be a very major breakthrough in designing quantum algorithms.
- 7y ago
- PabloGranolabar 7y agoThis is not good advice at all. Reducing rounds to increase performance is going to significantly weaken the cipher if obfuscation is the key. And new attack vectors, especially with the advent of cheap cloud storage (rainbow tables), advances in GPU performance, and quantum computing are all necessary factors to consider. I wouldn't use Blake3 for anything after reading the above.