2014 Comparison Open Source Software Development 
ForAllSecure
NOVEMBER 24, 2020
In this episode I talk about how Heartbleed (CVE 2014-0160) was found and also interview Rauli Kaksonen, someone who was at Codenomicon at the time of its discovery and is now a senior security specialist at the University of Oulu in Finland, about how new security tools are still needed to find the next big zero day. No shame in that.
ForAllSecure
NOVEMBER 24, 2020
In this episode I talk about how Heartbleed (CVE 2014-0160) was found and also interview Rauli Kaksonen, someone who was at Codenomicon at the time of its discovery and is now a senior security specialist at the University of Oulu in Finland, about how new security tools are still needed to find the next big zero day. No shame in that.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
ForAllSecure
NOVEMBER 24, 2020
In this episode I talk about how Heartbleed (CVE 2014-0160) was found and also interview Rauli Kaksonen, someone who was at Codenomicon at the time of its discovery and is now a senior security specialist at the University of Oulu in Finland, about how new security tools are still needed to find the next big zero day. No shame in that.
ForAllSecure
MARCH 24, 2021
How could open source software be vulnerable for so long? And modern fuzzers are not random, they’re guided so they dynamically work their way through the code, increasing their code coverage to find unknown vulnerabilities that can escape other software testing such as static analysis. And it's a doozy program.
ForAllSecure
MARCH 24, 2021
How could open source software be vulnerable for so long? And modern fuzzers are not random, they’re guided so they dynamically work their way through the code, increasing their code coverage to find unknown vulnerabilities that can escape other software testing such as static analysis. And it's a doozy program.
ForAllSecure
APRIL 19, 2023
It was not a literal time machine, but a way of capturing the software development process by recording intervals and storing them in the close. Then, when a vulnerability was discovered later on, a developer could go back in time and find the moment the fault was introduced into the code. It's open source.
Expert insights. Personalized for you.
52 
Let's personalize your content