Re:Null pointer dereference – new security bug for OpenSSL
by Qantourisc on Thursday May 01, 2014 @06:16PM
(#7683009)
Is it me or should code that has to be secure be written in more manage languages to prevent these mistake ? (But managed languages probably have other security issues I don't know about ?)
[ Parent
| on HN ]
Re:Null pointer dereference – new security bug for OpenSSL
by pslam on Thursday May 01, 2014 @07:27PM
(#7683284)
If OpenSSL was written in a managed language, someone would need it in an environment a managed language wasn't suitable for, and end up porting it to C.
Re:Null pointer dereference – new security bug for OpenSSL
by dcsommer on Thursday May 01, 2014 @06:22PM
(#7683026)
Managed languages is one way to go, but they are not really appropriate for performance critical libraries like OpenSSL in my book. You can get safety without being managed in modern languages if the compiler does the safety proving for you (e.g. rustlang).
Re:Null pointer dereference – new security bug for OpenSSL
by akjj on Thursday May 01, 2014 @06:44PM
(#7683112)
Managed languages are very susceptible to timing attacks.
Re:Null pointer dereference – new security bug for OpenSSL
by Qantourisc on Friday May 02, 2014 @02:42AM
(#7684389)
For all clarity I meant like C++, ObjC, or others; any language that allows you to create things that enforce consistency during compile or runtime. (Like shared pointer and array containers.) Probably used the wrong terminology here.