If you want a safe interface that does not require passing random sizes around in extra arguments, this can also be done in C.
On Rust, it's pure love in 64 bit, I acknowledge that (I use Cosmic DE with Pop!_OS so I can relate) and evcode it's my main IDE, Crabcraft being second. But compiling 'simple' TUI tools on Rust it's impossible on 32 bit, even with ZRAM and a total of 1.5GB of RAM.
If you want half-secure TUI tools on 32 bit Golang it's a saner option than C/C++ and the only actual altual alternative to Rust. For instance AERC can be safer than Mutt to read email, even under a Maildir mailbox and email fetched/sent with isync/msmtp.
Like time-constant, and it's hard to be time-constant in a performance optimised language like Rust. LLVM is doing some magic, and you don't want any magic in a crypto library.
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