feature: Add OpenSSL FIPS provider #186
Merged
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.
Issue #, if available: #161
Description of changes:
Adding OpenSSL FIPS provider. We will install OpenSSL using conda-forge to ensure compatibility with all packages, however the latest FIPS-verified provider is from OpenSSL 3.0.8. Followed these instructions for installing FIPS-verified provider on top of existing OpenSSL installation, which involves fetching source code for both installed and verified versions, testing the verified providers against the installed version, then installing just the FIPS provider from 3.0.8.
For testing, build new v0 and v1 image and ran following commands on cpu and gpu for both, with same outputs all around. This tests listing providers before and after enabling FIPS, and then trying a non-FIPS algorithm (md5) to make sure it works before enabling, and doesn't work after:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.