[8.18](backport #6565) FIPS Build #7078
Open
+298
−28
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
Adds FIPS env var to magefile to enable FIPS compliant binary builds using the microsoft/go toolchain. (cherry picked from commit b20efc1)
mergify
bot
requested review from
pkoutsovasilis and
kaanyalti
and removed request for
a team
github-actions
bot
added
technical debt
Team:Elastic-Agent-Control-Plane
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
v1v
requested changes
Feb 28, 2025
⏳ Build in-progress, with failures
Failed CI Steps |
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.
What does this PR do?
Adds
FIPSenv var to magefile to enable FIPS compliant builds using the microsoft/go toolchain.This PR will not be sufficient to ensure that every artifact made with these changes are compliant, we still need to verify our crypto use.
Why is it important?
FIPS artifacts must be built with compliant toolchains.
Checklist
I have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry in./changelog/fragmentsusing the changelog toolI have added an integration test or an E2E testDisruptive User Impact
None
How to test this PR locally
Assuming microsoft go is available, run
FIPS=true mage build:binaryThis is an automatic backport of pull request #6565 done by [Mergify](https://mergify.com).