|
|
|
|
|
|
by jplayer01
2531 days ago
|
|
|
It makes sense to me. The article is all about how a significant percentage of all vulnerabilities are memory-related. With the rise of fuzzing, finding these vulnerabilities has become far easier to do and to automate (you can run fuzzers 24/7 and come up with plenty of attack vectors given enough time). So his final conclusion is "start to explore and invest in ways to replace every legacy C dependency you are currently using. Write a deprecation roadmap. Cut down your dependencies on Linux distributions." And from that logical chain to the conclusion follows the title. It could be seen as a form of editorializing though, so it could be argued that it should be changed to the original just based on that. |
|
|
FWIW it's the title / tagline the author themselves used when they posted the article on twitter, and I thought it was much clearer than the "official" title of "Fuzz rising".