-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fips feature: appears to use rand chacha #529
Comments
I'd theorise that this is rustls-ffi/librustls/src/crypto_provider.rs Line 513 in 7bb2ae7
rand crate) altogether.
|
My original API for the ECH GREASE left this up to the caller and during review it was suggested to pick it randomly internal to rustls-ffi. We could go back to something closer to that original idea. |
Fixed in main. Thanks! |
When built in fips feature mode, I expect entropy to be gathered by the FIPS module i.e. aws_lc_fips_0_13_0_RAND_priv_bytes such that it can use any appropriated source of entropy, with FIPS approved (ACVP tested) conditioning functions if any (ie. SHA3).
Or forexample use kernel / OS entropy source, i.e. getrandom.
During the build it appears that rand / rand_chacha are pulled in, and as far as I understand CHACHA is not FIPS approved functionality
Can you explain why/how rand_chacha is pulled into a fips build of librustls? Can it be avoided in-favour of using aws_lc_fips functions for randomness? (i.e. RAND_priv_bytes and similar)?
The text was updated successfully, but these errors were encountered: