4 ms·

Relevant: https://groups.google.com/forum/#!topic/Golang-Nuts/0za-R3wVaeQ https://groups.google.com/forum/#!topic/Golang-Nuts/0za-R3wV... JT Olds asks: "Why di

Relevant: https://groups.google.com/forum/#!topic/Golang-Nuts/0za-R3wVaeQ https://groups.google.com/forum/#!topic/Golang-Nuts/0za-R3wV... JT Olds asks: "Why did Go implement its own SSL library? I've scanned the list and the website and I might have missed a design doc somewhere, but as far as I can tell I can't find any motivational reason for why Go implemented its own SSL library." agl responds: "Have you seen the OpenSSL code? I do, indeed, work with it a lot and it doesn't exactly fill one with positive feelings. NSS has a different set of issues. (I'm not familiar with alternatives like Polar or GnuTLS.)"

al2o3cr 13y ago
Nothing like rejecting all the alternatives and getting a brand-new shiny set of security holes, amirite?
- chubot 13y ago
  Since Go's SSL library written in Go, it should be a lot more resistant Heartbleed-type errors. In Go you use slices to manipulate memory, which are basically (pointer, length, capacity) triples (IIRC). This is a nice feature of Go -- a new balance between safety and performance.