C-WCOW: Enforce hashes on already mounted CIMs #2556
+131
−14
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
micromaomao
reviewed
Nov 17, 2025
MahatiC
force-pushed
the
enforce-hashes
branch
from
9994456 to
40ae7cb
Compare
MahatiC
force-pushed
the
enforce-hashes
branch
from
40ae7cb to
b606172
Compare
anmaxvl
reviewed
Jan 14, 2026
MahatiC
force-pushed
the
enforce-hashes
branch
3 times, most recently
from
3c87763 to
1758527
Compare
anmaxvl
approved these changes
Jan 26, 2026
MahatiC
force-pushed
the
enforce-hashes
branch
5 times, most recently
from
3df5e5b to
33dfbbd
Compare
helsaawy
approved these changes
Jan 29, 2026
Contributor
|
needs a rebase. |
Signed-off-by: Mahati Chamarthy <mahati.chamarthy@gmail.com>
Signed-off-by: Mahati Chamarthy <mahati.chamarthy@gmail.com>
Signed-off-by: Mahati Chamarthy <mahati.chamarthy@gmail.com>
MahatiC
force-pushed
the
enforce-hashes
branch
from
33dfbbd to
2f44bbc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Prior to this change, if you had two containers with the same image layers, the second container would not get captured in the SecurityPolicy metadata and hence would not enforce the policy. SecurityPolicy pkg captures container image layer hashes and associates them with the ContainerID during CIM mount operation. But because the CIMs are already mounted (for the previous container), this process would not occur for the second container with the same layers.
This change caches the image layer hashes for each container and SecurityPolicy instance will capture it in the metadata later on (during layer combining) if it wasn't already captured previously for this ContainerID and enforces policy.