linux-kernel - Re: [PATCH 0/4] 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:	Wed, 08 Oct 2008 10:19:44 -0400
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	James Morris <jmorris@...ei.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Hellwig <hch@...radead.org>,
	Al Viro <viro@...IV.linux.org.uk>,
	David Safford <safford@...son.ibm.com>,
	Serge Hallyn <serue@...ux.vnet.ibm.com>
Subject: Re: [PATCH 0/4] integrity

On Wed, 2008-10-08 at 15:56 +1100, James Morris wrote:
> On Tue, 7 Oct 2008, Mimi Zohar wrote:
> 
> >   The integrity-TPM-internal-kernel-interface.patch prereqs:
> >         TPM-update-char-dev-BKL-pushdown.patch
> >         TPM-num_opens-to-is_open-variable-change.patch
> >         TPM-rcu-locking.patch
> >         TPM-addition-of-pnp-remove.patch
> >         TPM-Fixed-tpm_release-timing.patch
> 
> Where are these patches?
> 
> i.e. are they in a tree?  If so, which one?  If not, they need to be 
> posted in this series.
> 
> 
> 
> - James

The TPM patches have not, as yet, been picked up.

These TPM patches are base TPM changes, not really related to the
integrity patches and certainly not dependent them.  However the reverse
is not true.  The integrity-tpm-internal-kernel-interface patch is
dependent on, at least, the TPM-rcu-locking patch.

Mimi

--
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/