Re:A Rust-based TLS library outperformed OpenSSL in almost e...
by pcwalton on Friday July 19, 2019 @02:33PM
(#20481269)
Brian Smith is well-regarded as an expert in this field. He knows what he's doing.
[ Parent
| on HN ]
Re:A Rust-based TLS library outperformed OpenSSL in almost e...
by drenvuk on Friday July 19, 2019 @02:39PM
(#20481330)
Just trusting a name and not the product has led to some bad outcomes before.
Re:A Rust-based TLS library outperformed OpenSSL in almost e...
by bluejekyll on Friday July 19, 2019 @02:50PM
(#20481435)
Having worked with Brian while integrating ring into Trust-DNS, I concur with the assessment from pcwalton.
But, yes, the name isn’t the only thing, but the discourse on the development of ring through the issue discussion on Github is high quality and very conservative in what is accepted. The library is high quality and has decent test coverage, with a diligent review process. All of that stems from Brian’s effort in maintaining an amazing project.
Re:A Rust-based TLS library outperformed OpenSSL in almost e...
by tptacek on Friday July 19, 2019 @04:49PM
(#20482329)
Can you provide an example of a name trusted among cryptographers, a specific library, and a bad outcome? I agree with Patrick Walton: Brian Smith is an extremely credible engineer in this particular domain.
I would venture, tentatively, the hypothesis that the exact opposite thing is true, and that trusting well-established subject matter experts has been a pretty good strategy in cryptographic security. There's a reason everyone uses Sodium/Nacl.
Re:A Rust-based TLS library outperformed OpenSSL in almost e...
by tedunangst on Friday July 19, 2019 @09:08PM
(#20483607)
I think the subject is somewhat ambiguous because for many users, they are more likely to recognize library author names than cryptographers. And imagine those authors are cryptographers in their own right.