-
Notifications
You must be signed in to change notification settings - Fork 113
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
Fix fips-compat build #296
Conversation
6225f43
to
38dac45
Compare
I'm not sure I follow, but AFAICT this change kind of defeats the purpose of The point of |
|
Oh, I see what you mean. I think the missing context here is that Though this is clearly not documented properly. An alternative fix would be to switch the BoringSSL source to |
Oh, I see. I misunderstood this as testing the FIPS API without the FIPS build (because e.g. it's not possible to build FIPS on macOS any more — the newest FIPS-certified clang is older than the oldest Apple-supported clang). |
Because
fips
feature impliesfips-compat
, the negation needs to benot(fips-compat)
. Except for the ABI changes, which change only with thefips
feature.Just to be safe, I've used
.try_into().unwrap()
in FFI instead of assert + casts.try_into()
will be optimized out when it really doesn't matter.