Remove Comparison Remove Malware Remove Programming Remove Software Development
article thumbnail

The Hacker Mind Podcast: Hunting The Next Heartbleed

ForAllSecure

Fuzzing involves sending invalid input to stress test software - either the program can handle the invalid input or it can’t. Gibberish was being imputed and the program sometimes did and did not behave as expected. I got my start writing about malware, this was back even before the term malware existed.

article thumbnail

The Hacker Mind Podcast: Hunting The Next Heartbleed

ForAllSecure

Fuzzing involves sending invalid input to stress test software - either the program can handle the invalid input or it can’t. Gibberish was being imputed and the program sometimes did and did not behave as expected. I got my start writing about malware, this was back even before the term malware existed.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

The Hacker Mind Podcast: Hunting The Next Heartbleed

ForAllSecure

Fuzzing involves sending invalid input to stress test software - either the program can handle the invalid input or it can’t. Gibberish was being imputed and the program sometimes did and did not behave as expected. I got my start writing about malware, this was back even before the term malware existed.

article thumbnail

Technology Short Take 139

Scott Lowe

This Technology Short Take is a bit heavy on cloud, OS, and programming topics, but there should be enough other interesting links to be useful to plenty of folks. (At Linux malware is getting more sophisticated. Programming. Welcome to Technology Short Take #139! At least, I hope that’s the case!) Networking.

Vmware 60
article thumbnail

The Hacker Mind Podcast: EP 69 Self-Healing Operating Systems

ForAllSecure

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. He called it Time Stone.