Update build-fips target for FIPS 140-3 compliance#302
Open
PrymalInstynct wants to merge 1 commit intosmallstep:mainfrom
Open
Update build-fips target for FIPS 140-3 compliance#302PrymalInstynct wants to merge 1 commit intosmallstep:mainfrom
PrymalInstynct wants to merge 1 commit intosmallstep:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Name of feature:
Update for FIPS 140-3 compliance
Pain or issue this feature alleviates:
BoringCrypto is no longer the supported method for implementing FIPS 140 compliance as of Go version 1.24
Replacing deprecated options from
Makefilewith current FIPS 140 methodWhy is this important to the project (if not answered above):
Maintaining a common and supported method for compiling Step related projects with FIPS 140-3 support is critical for its use in high security environments.
Is there documentation on how to use this feature? If so, where?
N/A
In what environments or workflows is this feature supported?
N/A
In what environments or workflows is this feature explicitly NOT supported (if any)?
N/A
Supporting links/other PRs/issues:
N/A
💔Thank you!