Rust Shillforce piles on Curl Author

https://daniel.haxx.se/blog/2017/03/30/yes-c-is-unsafe-but/

>>12
ransomware has nothing to do with safe or unsafe languages, it's mostly about OS's security/access policies. it's about finding flaws in logic logic, not low-level exploitation. see also https://daniel.haxx.se/blog/2017/03/27/curl-is-c/

C is not the primary reason for our past vulnerabilities

There. The simple fact is that most of our past vulnerabilities happened because of logical mistakes in the code. Logical mistakes that aren’t really language bound and they would not be fixed simply by changing language.

>>22
OSes are also written in C

>>23
but the fact that an OS like Windows allows arbitrary programs to encrypt everthing on a HDD has nothing to do with C, type safety or memory safety. it has everything to do with access policies, which are language-agnostic.

fucking stupid Rustfags, security is not just buffer overflows

Rust is the future, goyim

>>24
Nigga u dum.
If ransomware got executed on a Windows PC, then it's either because the user is an idiot and ran a random exe file with administrator privileges, or it was due to an exploit.

WannaCry, for example, exploited a buffer overflow vulnerability to attack and spread https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0144
So yes it was because of C.

>>26
Isn't the overflow just what let it spread between computers on the same network?