RFC Integrity Service and SLIM
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest5 of 6 patches 13 repliesIn review
5 of 6 patches are in this archive. The cover letter announces 6.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | mprotect patch for use by SLIMinclude/ mm/ | +14 | 1 reply | |
| 2/6 | Integrity Service API and dummy providerinclude/ security/ security/ +2 more | +221 | 0 replies | |
| 3/6 | SLIM main patchsecurity/ | +1536 | 11 replies | |
| 4/6 | slim: secfs patchsecurity/ | +73 | 1 reply | |
| 6/6 | SLIM: debug outputsecurity/ security/ security/ | +550 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/6] Integrity Service and SLIM
This is an updated request for comments on a proposed integrity service framework and dummy provider, along with SLIM, a low water-mark mandatory access control LSM module which utilizes the integrity services as additional input to the access control decisions.
The latest fixes include:
- SLIM: Locking overhaul
- All: Update to 2.6.18-rc1 kernel
Later we will be submitting EVM as a specific integrity service provider under this proposed framework. By separating the submissions, we hope that the integrity framework and its relationship to SLIM (and potentially to selinux) will be clearer and easier to review. Since this integrity provider is a dummy, it has no requirements for TPM hardware, or for LSM stacking, again making the review simpler.
A corresponding userspace utility package is available at
http://www.research.ibm.com/gsal/tcpa
Patch 1/6 is a tiny patch to make mprotect available for revocation
Patch 2/6 provides the integrity service API with dummy provider.
Patch 3-6 provide SLIM, and a more detailed description of its changes, and points out its use of the integrity service.
These patches have no prerequisites for stacker or TPM related patches.