News for hackers. Stuff that matters.
Re:A Rust-based TLS library outperformed OpenSSL in almost e... by ori_b on Friday July 19, 2019 @02:56PM (#20481483)
Yeah, but not surprising: OpenSSL is generally considered to be rather poorly written, from reinventing their own memory allocators, poorly, to layers upon layers of performance-sucking wrappers, to just bizzare and convoluted design decisons.

I'd be far more interested in seeing comparisons to, eg, BearSSL.

Re:A Rust-based TLS library outperformed OpenSSL in almost e... by tptacek on Friday July 19, 2019 @07:04PM (#20483156)
Note well: that was the prevailing (and probably correct) opinion a few years ago, but OpenSSL's quality has by most accounts improved dramatically over the last few years. I wouldn't talk someone out of using BearSSL, but if you're writing code that has to depend on a C-language TLS library, OpenSSL is a sane first choice.
Re:A Rust-based TLS library outperformed OpenSSL in almost e... by bluejekyll on Friday July 19, 2019 @11:01PM (#20483935)
I’ve reviewed OpenSSL code somewhat recently and agree that it’s vastly improved.

Though, if you want something based on Rustls with C bindings (I have no involvement in this project) there is: https://github.com/mesalock-linux/mesalink

That’s OpenSSL compatible bindings into Rustls.

Re:A Rust-based TLS library outperformed OpenSSL in almost e... by mschuster91 on Friday July 19, 2019 @06:00PM (#20482802)
The thing is openssl runs on so many platforms, which may or may not guarantee anything except a barely working malloc/free, so it makes sense to ship a custom allocator.
Re:A Rust-based TLS library outperformed OpenSSL in almost e... by ori_b on Friday July 19, 2019 @06:28PM (#20482959)
Which ones?