It seems like this project would run into the same issues that the hypothetical pure-Rust version of OpenSSL would run into. Namely, that crypto code often needs to run in constant time, regardless of input, in order to not be vulnerable to timing attacks. As I understand it, Rust isn't capable of generating executables that run in constant time because of limitations in LLVM. There seems to be an RFC [1] to enable this sort of thing, but it's over a year old and doesn't seem to have moved much.
Is there any reason why a project like this would be immune to timing attacks whereas an SSL implementation wouldn't? Otherwise, a project like this seems like it's just asking for a vulnerability that's not fixable.
Is the current situation any different than with C? I'm not aware of any C language (or gcc/clang extension) equivalent of the proposed #[constant_time] annotation/verification.
Is there any reason why a project like this would be immune to timing attacks whereas an SSL implementation wouldn't? Otherwise, a project like this seems like it's just asking for a vulnerability that's not fixable.
[1] https://github.com/rust-lang/rfcs/issues/847