[1.1] libcontainer: force apps to think fips is enabled/disabled for testing #4257
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
sohankunkerkar
force-pushed
the
release-1.1
branch
3 times, most recently
from
41886f9
to
58e308b
Compare
sohankunkerkar
changed the title
The motivation behind this change is to provide a flexible mechanism for containers within a Kubernetes cluster to opt out of FIPS mode when necessary. This change enables apps to simulate FIPS mode being enabled or disabled for testing purposes. Users can control whether apps believe FIPS mode is on or off by manipulating `/proc/sys/crypto/fips_enabled`. Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
sohankunkerkar
force-pushed
the
release-1.1
branch
from
58e308b
to
6379b58
Compare
mrunalp
approved these changes
Apr 26, 2024
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.
This is a backport of #4246 to release-1.1. Original description follows.
The motivation behind this change is to provide a flexible mechanism for containers within a Kubernetes cluster to opt out of
FIPSmode when necessary. This change enables apps to simulateFIPSmode being enabled or disabled for testing. Users can control whether apps believeFIPSmode is on or off by manipulating/proc/sys/crypto/fips_enabled.