dm-devel:dm-crypt: infrastructure for measurement of DM target data using IMA
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 Latest2 patches 0 repliesNew
- v32 patches 2 repliesSuperseded
- v22 patches 0 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 | 2 patches | 2 replies | Superseded |
Changes in v4 from the cover letter
Incorporated feedback from Milan Broz <[email protected]> on v3 series.
- Added device name of both base disk and target device for measurement, along with their major:minor.
- Introduced a function get_devname_from_maj_min() in dm-ima.c, to get the device name from device major:minor. Currently it is used for dm-crypt measurements, but it would be helpful for measuring other device-mapper targets as well.
- Added dm_target members - len and begin - to measurement list.
- Taken dependency on the updated base series v4 (1. above)
- Taken dependency on the updated early boot measurement series v3 (2. above).
Patches in v4 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | dm-devel: collect target data and submit to IMA to measureblock/ drivers/ drivers/ +2 more | +449 | 0 replies | |
| 2/2 | dm-crypt: collect data and submit to DM to measuredrivers/ security/ security/ | +220 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.
Cover letter [PATCH v4 0/2] dm-devel:dm-crypt: infrastructure for measurement of DM target data using IMA
There are several device-mapper targets which contribute to verify the integrity of the mapped devices e.g. dm-integrity, dm-verity, dm-crypt etc.
But they do not use the capabilities provided by kernel integrity subsystem (IMA). For instance, the IMA capability that measures several in-memory constructs and files to detect if they have been accidentally or maliciously altered. IMA also has the capability to include these measurements in the IMA measurement list and use them to extend a TPM PCR so that they can be quoted. These TPM PCR extend operations ensure that the tampering with the order of constructs being measured, and tampering with the measured constructs themselves - doesn't go undetected. In general, this capability is used for remote attestation of in-memory constructs and files of interest. As of today,device-mapper targets don't use the benefits of extended TPM PCR quotes and ultimately the benefits of remote attestation.
This series bridges this gap, so that all device-mapper targets could take advantage of IMA's measuring and quoting abilities - thus ultimately enabling remote attestation for device-mapper targets.
This series is based on the following repo/branch:
repo: https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git
branch: next-integrity
commit aa662fc04f5b ("ima: Fix NULL pointer dereference in ima_file_hash")
This series also has a dependency on the following patch series and should be applied in the following order:
1. https://patchwork.kernel.org/patch/11795559/
2. https://patchwork.kernel.org/patch/11801525/
Change Log v4:
Incorporated feedback from Milan Broz <[email protected]> on v3 series.
- Added device name of both base disk and target device for measurement, along with their major:minor.
- Introduced a function get_devname_from_maj_min() in dm-ima.c, to get the device name from device major:minor. Currently it is used for dm-crypt measurements, but it would be helpful for measuring other device-mapper targets as well.
- Added dm_target members - len and begin - to measurement list.
- Taken dependency on the updated base series v4 (1. above)
- Taken dependency on the updated early boot measurement series v3 (2. above).
Change Log v3:
- Added dm-crypt as a supported data source to measure in ima.h.
- Taken dependency on the updated base series v3 (2. above)
- Taken dependency on the updated early boot measurement series v2 (3. above).
Change Log v2:
- Removed the references to "local" measurement from the description - as this series only support remote attestation, and not local integrity enforcement.
- Taken dependency on the updated base series (2. above), which introduced a boolean parameter measure_buf_hash as per community feedback to support measuring hash of the buffer, instead of the buffer itself.
- Taken dependency on the updated early boot measurement series (3. above).
Tushar Sugandhi (2):
dm-devel: collect target data and submit to IMA to measure
dm-crypt: collect data and submit to DM to measure
block/genhd.c | 2 + drivers/md/Makefile | 1 + drivers/md/dm-crypt.c | 217 ++++++++++++++ drivers/md/dm-ima.c | 378 ++++++++++++++++++++++++ include/linux/device-mapper.h | 67 +++++ include/linux/genhd.h | 1 + security/integrity/ima/ima.h | 1 + security/integrity/ima/ima_queue_data.c | 3 +- 8 files changed, 669 insertions(+), 1 deletion(-) create mode 100644 drivers/md/dm-ima.c
Signature · 1 line
2.17.1