You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rustls presently offers post quantum hybrid X25519MLKEM768 via a separate crate that augments the aws-lc-rs CryptoProvider with the post-qc algorithms, rustls-post-quantum. The plan is to eventually roll this into the main crate (rustls/rustls#2056).
Previously I prototyped a FFI wrapper around this provider in cpu/rustls-post-quantum-ffi as a means of verifying external crypto providers worked with the FFI crypto provider API in this crate.
I think it makes sense to roll the FFI wrapper for the post-qc provider into the main rustls-ffi crate and offer it behind a default-off opt-in feature ala fips or cert-compression. Once the rustls-post-quantum crate is rolled into the main rustls crate and offered by default we can do the same for rustls-ffi.
The text was updated successfully, but these errors were encountered:
Rustls presently offers post quantum hybrid X25519MLKEM768 via a separate crate that augments the aws-lc-rs
CryptoProvider
with the post-qc algorithms, rustls-post-quantum. The plan is to eventually roll this into the main crate (rustls/rustls#2056).Previously I prototyped a FFI wrapper around this provider in cpu/rustls-post-quantum-ffi as a means of verifying external crypto providers worked with the FFI crypto provider API in this crate.
I think it makes sense to roll the FFI wrapper for the post-qc provider into the main rustls-ffi crate and offer it behind a default-off opt-in feature ala
fips
orcert-compression
. Once therustls-post-quantum
crate is rolled into the main rustls crate and offered by default we can do the same forrustls-ffi
.The text was updated successfully, but these errors were encountered: