pipelines: go: add assert-no-crypto check #74719
Open
+26
−7
Conversation
This file contains hidden or 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
Add the go/assert-no-crypto pipeline to check that a Go module build does not import any crypto packages. Package builds can use that to ensure they are usable in FIPS context. This takes the code of the check from gops.yaml in preparation of further use. Signed-off-by: Markus Boehme <markus.boehme@chainguard.dev>
Member
Author
|
epoch-bot is failing, but I'm intentionally not bumping the epoch since this is a build-time check that is not affecting the output. |
Member
please bump the epoch - the rebuild is cheap; and we want to see the CI run to see that the build passes with this change. |
The new go/assert-no-crypto pipeline is using the open-coded check from gops.yaml verbatim. Switch to using the pipeline instead. Signed-off-by: Markus Boehme <markus.boehme@chainguard.dev>
To be able to use iptables-wrappers in a FIPS context, ensure it is not using any cryptography. Signed-off-by: Markus Boehme <markus.boehme@chainguard.dev>
markusboehme
force-pushed
the
go-assert-no-crypto
branch
from
47efa84 to
ad83df5
Compare
octo-sts
bot
added
the
bincapz/pass
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Move the no-cryptography check from
gops.yamlinto the newgo/assert-no-cryptopipeline. Then use it to ensure the build ofiptables-wrapperscan be used in an environment requiring FIPS compliance.