Google Releases Tool To Find Common Crypto Bugs (onthewire.io)
Trailrunner7 quotes a report from On the Wire: Google has released a new set of tests it uses to probe cryptographic libraries for vulnerabilities to known attacks. The tests can be used against most kinds of crypto algorithms and the company already has found 40 new weaknesses in existing algorithms. The tests are called Project Wycheproof, and Google's engineers designed them to help developers implement crypto libraries without having to become experts. Cryptographic libraries can be quite difficult to implement and making errors can lead to serious security problems. Attackers often will look for weak crypto implementations as a means of circumventing strong encryption in a target app. Among the issues that Google's engineers found with the Project Wycheproof tests is one in ECDH that allows an attacker to recover the private key in some circumstances. The bug is the result of some libraries not checking the elliptic curve points that they get from outside sources. "In cryptography, subtle mistakes can have catastrophic consequences, and mistakes in open source cryptographic software libraries repeat too often and remain undiscovered for too long. Good implementation guidelines, however, are hard to come by: understanding how to implement cryptography securely requires digesting decades' worth of academic literature. We recognize that software engineers fix and prevent bugs with unit testing, and we found that many cryptographic issues can be resolved by the same means," Daniel Bleichenbacher and Thai Duong, security engineers at Google, said in a post announcing the tool release. "Encodings of public keys typically contain the curve for the public key point. If such an encoding is used in the key exchange then it is important to check that the public and secret key used to compute the shared ECDH secret are using the same curve. Some libraries fail to do this check," Google's documentation says.
Google's engineers designed them to help developers implement crypto libraries without having to become experts .
I'm not sure if I am supposed to be happy or depressed about this claim...
It would be nice if they found a bug in Wikileaks' insurance files encryption algo...
the first rule of crypto is don't write your own crypto.
I've been programming security-related systems for 20 years. There's no chance I'd ever roll my own crypto. Tools to crack crypto? Yeah I do those. Write an IPSec / IKE implementation from scratch? I did that last week. You bet your ass it uses standard crypto libraries; I'm not writing those.
I don't feel like deploying a RADIUS server at home - it'd be nice if some router came with effective wifi encryption out of the box. Given a reasonable and secure solution, I'm sure M$ and 'NIX types would be happy to write the appropriate drivers to support it.
The site hosting the article has an expired ssl certificate! Oh the irony =)
It might help if Google had an add-on to E-Mail and Google that specifically checked ALL software that entered the system for Crypto Bugs!
I've been programming security-related systems for 20 years. There's no chance I'd ever roll my own crypto. Tools to crack crypto? Yeah I do those. Write an IPSec / IKE implementation from scratch? I did that last week. You bet your ass it uses standard crypto libraries; I'm not writing those.
These tools are still useful, to detect bugs in the libraries. Daniel and Thai have found a lot of those, and getting the fixes upstreamed is surprisingly hard.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.