linux-kernel - Re: [PATCH 0/7] integrity

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 6 Feb 2009 09:37:50 +1100 (EST)
From:	James Morris <jmorris@...ei.org>
To:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Safford <safford@...son.ibm.com>,
	Serge Hallyn <serue@...ibm.com>
Subject: Re: [PATCH 0/7] integrity 

On Wed, 4 Feb 2009, Mimi Zohar wrote:

> This patchset contains the IMA integrity patches. The changes made since
> the last integrity posting are based on comments made by James Morris and
> Serge Hallyn.
> - removed test for NULL return code from securityfs_create_file/dir
> - alloc ima_template_entry before calling ima_store_template()
> - log ima_add_boot_aggregate failure
> - free invalid rule
> - add hook to increment opencount for /dev/zero shm
> - replaced hard coded string length with #define name
> - removed unused IMA_TEMPLATE_NAME_LEN
> 
> This patchset is dependent on the tpm-integrity-interface patch, which
> has been applied to the security-testing-2.6/#next.
> 
> Mimi Zohar (7):
>   integrity: IMA hooks
>   integrity: IMA as an integrity service provider
>   integrity: IMA display
>   integrity: IMA policy
>   integrity: IMA policy open
>   Integrity: IMA file free imbalance
>   Integrity: IMA update maintainers

All applied to security-testing.


-- 
James Morris <jmorris@...ei.org>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/