7 ms·
Speaking of OpenSSL, what state are the competing libraries in at the moment? I'd love a version of OpenSSL without all the potentially-insecure legacy code giv
by josephg 12y ago
Speaking of OpenSSL, what state are the competing libraries in at the moment? I'd love a version of OpenSSL without all the potentially-insecure legacy code given all the problems its had.
Are there decent implementations of OpenSSL in more secure languages like Rust?
- gecko 12y agoF# has a proven implementation, but I doubt that's what you're after. OCaml is also getting one for Mirage, but I don't know its status, and it won't be proven correct.
- gsnedders 12y agomiTLS considers timing attacks as out of scope for the proof, so it's unclear if it's actually secure.
- deleted 12y ago[deleted]
- TheLoneWolfling 12y agoThere's LibreSSL: http://www.libressl.org/ http://www.libressl.org/ But it's not in a more secure language.
- nulterm 12y agoPast Discussion about Ocaml-TLS[1] also mentions Rust somewhere. [1] https://news.ycombinator.com/item?id=8005130 https://news.ycombinator.com/item?id=8005130
- meowface 12y agoA full rewrite of OpenSSL in a better language like Rust will probably take a very long time to be production ready. Your best middleground is LibreSSL, which is still C but is at least written by developers with huge amounts of experience writing secure C.
- trippy_biscuits 12y agoDo people really believe in more secure languages? Are they the same people that think switches make networks secure? Switches don't and neither does a given language. I recall a CTO that would not allow C++ development because he thought the language was insecure. Java was the only language allowed. Even college courses are still teaching that security is one of the benefits of the virtual machine. We only have to look at all the patches for java to see that it hasn't been secure. Then we look at every other software that has been patched to see that nothing is secure. Please stop perpetuating the myth that security is produced by a programming language. People make security happen just like they make it not happen. Obligatory Schneier: https://www.schneier.com/blog/archives/2008/03/the_security_mi_1.html https://www.schneier.com/blog/archives/2008/03/the_security_...
- lbarrow 12y agoI don't think security is produced by picking one language or another, but I do believe that it's harder to write secure code in a language like C than a language like Java or Rust. There are simply way, way more ways to shoot yourself in the foot.
- AnthonyMouse 12y ago> I don't think security is produced by picking one language or another, but I do believe that it's harder to write secure code in a language like C than a language like Java or Rust. There are simply way, way more ways to shoot yourself in the foot. The trouble is that everything is a trade off. It's very hard to get a buffer overrun in Java but that doesn't make Java a good language. It tries so hard to keep you from hanging yourself that it won't let you have any rope, so in the instances when you actually need rope you're forced to create your own and hang yourself with that. For example, you're presented with garbage collection and then encouraged to ignore object lifetime. There are no destructors to clean up when an object goes out of scope. But when it does you still have to cleanup open files or write records to the database or notify network peers etc. Which leaves you to have to manage it manually and out of order, leading to bugs and race conditions. In other words, C and C++ encourage you to write simple dangerous bugs while Java encourages you to write complicated dangerous bugs. That isn't to say that some languages don't have advantages over others, but rather that the differences aren't scalar. And code quality is by far more important than the choice of language. BIND would still be less secure than djbdns even if it was written in Java.
- willglynn 12y agoGo has a TLS package and dependencies which are almost entirely written in Go: http://golang.org/pkg/crypto/tls/ http://golang.org/pkg/crypto/tls/
- Aissen 12y agoGo's TLS stack is very nice but beware of the default tlsConfig (containing insecure 3DES and RC4 algorithms): https://wiki.mozilla.org/Security/Server_Side_TLS#Go https://wiki.mozilla.org/Security/Server_Side_TLS#Go Also, it might be vulnerable to side-channel timing attacks: https://www.imperialviolet.org/2013/02/04/luckythirteen.html https://www.imperialviolet.org/2013/02/04/luckythirteen.html