[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59b88042-9c56-c891-f75e-7c0719eb5ff9@linux.ibm.com>
Date: Mon, 7 Oct 2019 18:13:01 -0400
From: Ken Goldman <kgold@...ux.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
"Safford, David (GE Global Research, US)" <david.safford@...com>
Cc: 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()
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.
On 10/6/2019 8:05 PM, Jarkko Sakkinen wrote:
>
> Kernel has the random number generator for two reasons:
>
> 1. To protect against bugs in hwrng's.
> 2. To protect against deliberate backdoors in hwrng's.
>
> How TPM RNG is guaranteed to protect against both 1 and 2?
Powered by blists - more mailing lists