Comment on OpenSSL after HeartbleedparentComments−mSparks9yIt's not a case of blaming. Its a case of choosing https://www.libressl.org/ or https://www.openssl.org/Applying best practice development processes or Pretending someone else can do it all for you, and you can "bolt it on" at the end.The article lists: Future plans and lessons learned: At the top of the list for future development is support for TLS 1.3.Like adding yet another protocol to the already hacked mess of protocols is a "good" thing.−DasIch9yLibreSSL is only better because it does less and much more human attention is wasted on producing bug free C code. That's an improvement but it's quite limited.
Comments
It's not a case of blaming. Its a case of choosing https://www.libressl.org/ or https://www.openssl.org/
Applying best practice development processes or Pretending someone else can do it all for you, and you can "bolt it on" at the end.
The article lists: Future plans and lessons learned: At the top of the list for future development is support for TLS 1.3.
Like adding yet another protocol to the already hacked mess of protocols is a "good" thing.
LibreSSL is only better because it does less and much more human attention is wasted on producing bug free C code. That's an improvement but it's quite limited.