Meanwhile, ring [2] carries an explicit disclaimer of "This is an experiment".
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.
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