4 ms·
> Safe and fast crypto implementations from Google's BoringSSL I'm a little confused, is this a wrapper on BoringSSL?
by MBlume 9y ago
> Safe and fast crypto implementations from Google's BoringSSL
I'm a little confused, is this a wrapper on BoringSSL?
- deleted 9y ago[deleted]
- pfg 9y agoMesaLink relies on ring for its crypto operations. Ring is written in a mix of Rust, C and assembly, with most of the C and assembly code coming from (Boring|Open)SSL.
- pcwalton 9y agoMy understanding is that MesaLink uses the low-level crypto from BoringSSL (transitively via ring) and the high-level protocol code from ring, which is written in Rust. Most memory safety problems in TLS implementations come from the higher-level protocol code, not the implementations of the raw crypto primitives. In fact, the latter benefit from being written in as low-level of a style as possible to mitigate timing attacks. Edit: Brian Smith has an authoritative comment here: https://www.reddit.com/r/rust/comments/89aiyw/mesalink_a_memorysafe_and_opensslcompatible_tls/dwqjdyo/ https://www.reddit.com/r/rust/comments/89aiyw/mesalink_a_mem...