Open
Conversation
nikhilbarge
force-pushed
the
topic/nbarge/fips-update
branch
from
e8b9180 to
6070e67
Compare
Contributor
|
Don't you also need to change or ensure docker image building the binaries are able to build using FIPS crypto? If so, please document how one would do that also. Something like https://github.com/microsoft/go/tree/microsoft/main/eng/doc/fips |
nikhilbarge
force-pushed
the
topic/nbarge/fips-update
branch
2 times, most recently
from
708bde2 to
fd7b544
Compare
nikhilbarge
force-pushed
the
topic/nbarge/fips-update
branch
from
fd7b544 to
07ec51b
Compare
kaovilai
reviewed
Dec 17, 2024
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
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.
What this PR does / why we need it:
Update to make velero vsphere plugin fips compliant
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: