Messages in this thread |  | | Subject | Re: [PATCH v7 00/16] EVM | | From | Mimi Zohar <> | | Date | Tue, 19 Jul 2011 16:56:11 -0400 |
| |
On Tue, 2011-07-19 at 09:52 +1000, James Morris wrote: > The discussion on this seems to have run its course. > > Does anyone have any further issues with these patches? > > Otherwise, I will merge EVM. > > > - James
James,
If/when you're ready to merge the EVM patches, they have been rebased against the latest security-testing-2.6/#next and a couple of whitespaces removed. No other changes were made.
The following changes since commit 0f2a55d5bb2372058275b0b343d90dd5d640d045:
TOMOYO: Update kernel-doc. (2011-07-14 17:50:03 +1000)
are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/zohar/ima-2.6.git next-evm
Dmitry Kasatkin (5): evm: add support for different security.evm data types evm: crypto hash replaced by shash evm: additional parameter to pass integrity cache entry 'iint' evm: evm_verify_hmac must not return INTEGRITY_UNKNOWN evm: replace hmac_status with evm_status
Mimi Zohar (11): security: new security_inode_init_security API adds function callback integrity: move ima inode integrity data management xattr: define vfs_getxattr_alloc and vfs_xattr_cmp evm: re-release security: imbed evm calls in security hooks evm: evm_inode_post_removexattr evm: imbed evm_inode_post_setattr evm: add evm_inode_init_security to initialize new files evm: call evm_inode_init_security from security_inode_init_security evm: permit only valid security.evm xattrs to be updated evm: add evm_inode_setattr to prevent updating an invalid security.evm
thanks,
Mimi
|  |