4 ms·
For every 1 security breach due to C++ memory management, there are at least 100000 due to shitty PHP code that doesn't escape strings or uses plaintext passwor
by otabdeveloper4 3y ago
For every 1 security breach due to C++ memory management, there are at least 100000 due to shitty PHP code that doesn't escape strings or uses plaintext passwords that never change. (This is a conservative estimate.)
- sirwhinesalot 3y agoPHP (the language) has long since moved past awful practices like that, and we can definitely tell people to stop doing that and use the provided safe alternatives instead. In fact, the PHP docs do just that. PHP is no longer to blame here. Also that number is greatly exaggerated. It's simply not true anymore, check the CVE website if you don't believe me.
- acdha 3y agoCan you cite your sources on that analysis? Be sure to include the relative affected numbers so we don’t count an exploit in Chrome the same as a PHP exploit affecting a dozen people using someone’s obscure WordPress plugin. Another way of thinking about this, why are all of the browser teams who have some of the best C++ developers in the world and significant resources adopting memory-safe languages? Nobody at that level is doing that because it’s cool, so there might be something to be learned from their reasoning.
- otabdeveloper4 3y ago> why are all of the browser teams who have some of the best C++ developers in the world and significant resources adopting memory-safe languages? They aren't. Even Mozilla abandonded their Rust-in-Firefox project.