upvote
If I am not mistaken, the default backend is aws-lc [1] which is... a C library (still better than having the frontend in C as well, though).

Meanwhile, ring [2] carries an explicit disclaimer of "This is an experiment".

[1] https://github.com/aws/aws-lc

[2] https://github.com/briansmith/ring

reply
The crypto primitives in OpenSSL have been pretty solid (although timing attacks come up from time to time).

Where OpenSSL has been bad to terrible over decades is protocol handling, api management, and lately locking.

Managing protocol in a more restrictive language is a good thing. Bonus if it has the potential to require less work from application developers around version updates. Maybe they got better, I was using <= 1.0.2; back then there was a chance some things would break between different letter releases on the same version number even though it still compiles, and going to a new version meant a lot of work.

reply
aws-lc is a lot of assembly, which you kinda need anyway. Neither Rust nor C are fully suitable for cryptography because common optimizing compiler backends (LLVM, GCC, MSVC) can introduce branches (even if you wrote it in a branchless manner!), making the crypto code vulnerable to side-channel attacks.

So the options are

  - write it in assembly
  - use a high-level language, then verify the generated assembly the compiler generates
  - write a new or modify an existing backend to support timing-independent code
aws-lc does the first, some other crypto libs try to do the 2nd but I don't know how solid that is and the 3rd one takes time.

base64 encode hopefully isn't used in places where it would be a timing channel, so it could still benefit from a safe Rust impl. And at least it's API could benefit from slices and Result

reply
You can also use a formally proven https://github.com/ctz/graviola/
reply