| ▲ | brianpane an hour ago | |
There’s already a Rust TLS library, rustls, that’s relatively mature (10 years in development, a couple of paid maintainers, robust development and release processes). It’s not a drop-in replacement for OpenSSL, though. There’s a companion project to build an OpenSSL-compatible wrapper API for it, but that’s not as far along. Interestingly, while rustls has a plug-in API that lets you choose your favorite Rust encryption library for the low-level operations (aws-lc-rs, Ring, Graviola, etc), those libraries all tend to contain a lot of assembly … not just for speed, but because it’s easier to avoid side channel timing vulnerabilities in assembly. | ||
| ▲ | zelphirkalt a few seconds ago | parent | next [-] | |
Can you explain why it is easier to avoid side-channel timing attacks in assembly? | ||
| ▲ | dralley 7 minutes ago | parent | prev [-] | |
The side channels issue is where rust crypto libraries are currently the weakest | ||