All of today's OpenSSL vulnerabilities are in code that was replaced long ago in *ring* & webpki, so nothing for me to do today. Boring.
@RichSalz @sleevi_ @davidben__ Anyway, let's not interpret me saying something good about *ring* as saying something bad about other forks.
-
-
@BRIAN_____@sleevi_@davidben__ sure no problem with that. -
@RichSalz@sleevi_@davidben__ Also, almost all of my 167+ of my BoringSSL patches are licensed under the OpenSSL license, for y'all to use. -
@BRIAN_____@sleevi_@davidben__ neat! where can we find them? -
@RichSalz@sleevi_@davidben__ The 167 number refers to the ones that already landed in BoringSSL: https://boringssl.googlesource.com/boringssl/ .
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.