2 ms·
ASN.1 is so well-understood at this point that Galois even has a high-assurance toolkit for it: http://cps-vo.org/node/1577 http://cps-vo.org/node/1577 Maybe
by nickpsecurity 11y ago
ASN.1 is so well-understood at this point that Galois even has a high-assurance toolkit for it:
http://cps-vo.org/node/1577 http://cps-vo.org/node/1577
Maybe someone should forward that to OpenSSL team and suggest they pay Galois to crank out a bunch of encoders/decoders for them for anything requiring that in OpenSSL. Or LANGSEC people behind HAMMER toolkit. Or even the Cap n Proto guy.
Seriously, the number of preventable failures in this software, esp memory, is a strong indicator of why you should never use it.
- peterwwillis 11y ago> Maybe someone should forward that to OpenSSL team and suggest they pay Galois Here's where you can donate your money to pay Galois: https://www.openssl.org/support/donations.html https://www.openssl.org/support/donations.html Once they've received the funds i'm sure they'll get right on it.
- nickpsecurity 11y agoLol. I thought they've had money all this time and not spent it on stuff that works. Meanwhile, LibreSSL did more in a few weeks for their code quality than its owners did in a year. Why would I give them money expecting something different? The right course, if we're talking Galois, is for them to try to ask Galois to donate some time or tooling to improve critical aspects of a widespread-deployed library. They already make money with grants and stuff for code they often open-source. They might even find thr deliverables useful for them. So OpenSSL team can feel free to give them a call.