unless you’re stating crypto primitives should only be written in assembly
Yes, that's exactly what I'm stating.
Have a look at openssl, boringssl, nspr, etc. They all implement the core modular arithmetic for RSA and the s-box table for AES using assembly language. There is no reliable way to prevent a C compiler from "optimizing" your constant-time code into non-constant-time code.
another rust TLS implementation
rustls uses assembler (from boringssl) for these routines. It is not 100% rust, and that's a good thing.
Yes, that's exactly what I'm stating.
Have a look at openssl, boringssl, nspr, etc. They all implement the core modular arithmetic for RSA and the s-box table for AES using assembly language. There is no reliable way to prevent a C compiler from "optimizing" your constant-time code into non-constant-time code.
another rust TLS implementation
rustls uses assembler (from boringssl) for these routines. It is not 100% rust, and that's a good thing.