[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191008234935.GA13926@linux.intel.com>
Date: Wed, 9 Oct 2019 02:49:35 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Ken Goldman <kgold@...ux.ibm.com>
Cc: "Safford, David (GE Global Research, US)" <david.safford@...com>,
Mimi Zohar <zohar@...ux.ibm.com>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"open list:ASYMMETRIC KEYS" <keyrings@...r.kernel.org>,
"open list:CRYPTO API" <linux-crypto@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] KEYS: asym_tpm: Switch to get_random_bytes()
On Mon, Oct 07, 2019 at 06:13:01PM -0400, Ken Goldman wrote:
> The TPM library specification states that the TPM must comply with NIST
> SP800-90 A.
>
> https://trustedcomputinggroup.org/membership/certification/tpm-certified-products/
>
> shows that the TPMs get third party certification, Common Criteria EAL 4+.
>
> While it's theoretically possible that an attacker could compromise
> both the TPM vendors and the evaluation agencies, we do have EAL 4+
> assurance against both 1 and 2.
Certifications do not equal to trust.
/Jarkko
Powered by blists - more mailing lists