Remove crypto/internal/boring/fipstls
dependency from crypto/internal/backend
#1441
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.
(Review ignoring whitespaces)
Upstream refactored the fipstls logic to support the new built-in FIPS module. This is causing many conflicts in the upstream sync PR.
This PR moved the logic that detects whether FIPS mode is required or not (e.g. setting the
GOFIPS
env var) to its own package that only depends onsyscall
. This way we can easily import it elsewhere, for example incrypto/internal/boring/fipstls
and makecrypto/internal/backend
not depend on the former. Doing so will greatly simplify reconciling the conflicts in the upstream sync PR.The refactor shouldn't change any behavior.
For #1416.
For #1383.