<a href="https://twitter.com/joshbressers" rel= "nofollow">Josh</a> and <a href="https://twitter.com/kurtseifried" rel="nofollow">Kurt</a> talk about the recent OpenSSL nothingburger. OpenSSL got everyone whipped into a frenzy over a critical vulnerability, then changed the severity to high. The correct solution to this whole problem is to stop using a TLS library written in C, we need to be using memory safe languages. Don't migrate from OpenSSL 1 to 3, migrate from OpenSSL 1 to Rustls. Show Notes <ul dir="auto"> <li><a href= "https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/" rel="nofollow">OpenSSL Blog Post</a></li> <li><a href= "https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html" rel="nofollow">OpenSSL pre-announcement</a></li> <li><a href= "https://twitter.com/iamamoose/status/1584908434855628800" rel= "nofollow">Mark Cox Tweet 3.0 only affected</a></li> <li><a href= "https://twitter.com/GossiTheDog/status/15860315723267973130" rel= "nofollow">GossiTheDog NDA Tweet</a></li> <li><a href= "https://twitter.com/GossiTheDog/status/1586054681159430144" rel= "nofollow">Claims of a name and logo</a></li> <li><a href="https://www.memorysafety.org/initiative/rustls/" rel= "nofollow">Rustls</a></li> </ul> <a href= "https://commons.wikimedia.org/wiki/File:LeadPaint1.JPG">Image Credit</a>

Episode 349 - The cyber is coming from inside the house - the UK is scanning itself

Open Source Security is a media project to help showcase and educate on open source security. Our goal is to give the community a platform educate both developers and users on how open source security works.

There's a lot of good work happening that doesn't get attention because there's no marketing department behind it, they don't have a developer relations team posting on LinkedIn every two hours. Let's focus on those people and teams then learn what they do and how they do it. The goal is to hear from the people doing the work, they know what's up, they have a lot to teach us. We just have to listen.