[fips] Add FIPS and non-FIPS implementations for allowed TLS curves #13992
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.
Description
This PR introduces a new Go build tag,
requirefips
, that can be used (in the future) to build a FIPS-capable distribution of the OTel Collector. This PR uses this new build tag to create FIPS (//go:build requirefips
) and non-FIPS (//go:build !requirefips
) implementations of allowed TLS curves. The FIPS implementation contains all the TLS curves as the non-FIPS implementation exceptX25519
andX25519MLKEM768
.If these two curves were included in the FIPS distribution, running it with Golang >=1.24.6 and
GODEBUG=fips140=only
to surface non-FIPS-compliant algorithm uses will result in errors like so:Link to tracking issue
Fixes #13990
Testing
Run the existing
confighttp.TestHttpReception
unit test with Go >= 1.24.6 andGODEBUG=fips140=only
to surface non-FIPS-compliant algorithm uses.Without the
requirefips
build tagWith the
requirefips
build tag