This shouldn't have happened: A vulnerability postmortem
Wow.<p>We continue to be reminded that it's hard to write fully memory secure code in a language that is not memory secure?<p>And by hard, I mean, very hard even for folks with lots of money and time and care (which is rare).<p>My impression is that Apple's imessage and other stacks also have memory unsafe languages in the api/attack surface, and this has led to remote one click / no click type exploits.<p>Is there a point at which someone says, hey, if it's very security sensitive write it in a language with a GC (golang?) or something crazy like rust? Or are C/C++ benefits just too high to ever give up?<p>And similarly, that simplicity is a benefit (ie, BoringSSL etc has some value).