Repository navigation
Initial support for verified CIMs - #2448
Merged
Merged
Conversation
Amit Barve (ambarve)
force-pushed
the
verified_cim_support
branch
2 times, most recently
from
June 3, 2025 14:48
de3af9f to
3b54c91
Compare
Amit Barve (ambarve)
marked this pull request as ready for review
June 3, 2025 14:49
Amit Barve (ambarve)
force-pushed
the
verified_cim_support
branch
4 times, most recently
from
June 9, 2025 20:36
7aed5d0 to
dc7cf5c
Compare
Amit Barve (ambarve)
force-pushed
the
verified_cim_support
branch
2 times, most recently
from
June 19, 2025 15:44
a8ec08d to
79c25dd
Compare
Kirtana Ashok (kiashok)
approved these changes
Jul 1, 2025
Amit Barve (ambarve)
force-pushed
the
verified_cim_support
branch
2 times, most recently
from
July 3, 2025 17:42
083a173 to
f448408
Compare
Scott Brender (msscotb)
approved these changes
Jul 8, 2025
Amit Barve (ambarve)
force-pushed
the
verified_cim_support
branch
2 times, most recently
from
July 8, 2025 20:45
4a293d0 to
4d8cf9e
Compare
Block CIMs can now provide integrity checking (via a hash/Merkel tree, similar to dm-verity on Linux). A block CIM written with integrity checking enabled is called a verified CIM. A verified CIM is written once and then sealed to prevent any further modifications. When such a CIM is sealed it returns a digest of its contents. Such a CIM can then be mounted by passing in this digest. Every read on that mounted volume will then be verified against this digest to ensure the integrity of the contents of that CIM. Signed-off-by: Amit Barve <ambarve@microsoft.com>
Amit Barve (ambarve)
force-pushed
the
verified_cim_support
branch
from
July 8, 2025 21:02
4d8cf9e to
5a1a2bb
Compare
Kirtana Ashok (kiashok)
approved these changes
Jul 8, 2025
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.
Block CIMs can now provide integrity checking (via a hash/Merkel tree, similar to dm-verity on Linux). A block CIM written with integrity checking enabled is called a verified CIM. A verified CIM is written once and then sealed to prevent any further modifications. When such a CIM is sealed it returns a digest of its contents. Such a CIM can then be mounted by passing in this digest. Every read on that mounted volume will then be verified against this digest to ensure the integrity of the contents of that CIM.