Refactor SetFIPS to support third-party FIPS providers #206
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qmuntal
requested review from
ueno,
karianna,
derekparker,
dagood,
mertakman and
gdams
qmuntal
removed request for
ueno,
karianna,
derekparker,
dagood,
mertakman and
gdams
qmuntal
requested review from
ueno,
karianna,
derekparker,
dagood,
mertakman and
gdams
karianna
approved these changes
Oct 22, 2024
dagood
reviewed
Oct 25, 2024
Co-authored-by: Davis Goodin <[email protected]>
dagood
approved these changes
Oct 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our current
openssl.SetFIPSimplementation only works with the built-in FIPS provide.This PR still tries to load the built-in FIPS provider as a best effort, but it only fails if there is no provider that supports the
-fips=yesquery.