From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Sakkinen Subject: Re: [PATCH v3 0/7] tpm: TPM2.0 eventlog securityfs support Date: Tue, 20 Sep 2016 13:04:23 +0300 Message-ID: <20160920100423.GB32433@intel.com> References: <1472532619-22170-1-git-send-email-nayna@linux.vnet.ibm.com> <20160830101611.GA11819@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tpmdd-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Stefan Berger , philip.b.tricca-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: tpmdd-devel@lists.sourceforge.net On Mon, Sep 19, 2016 at 10:50:15AM -0400, Stefan Berger wrote: > > You also fail to explain how this should work with ACPI even though > > we know that there does not exist any kind for event log through ACPI > > with TPM 2.0 hardware. I.e. just by reading the commits I can obviously > > see that you are doing major untested code path changes. > > That's true there there's not spec for a BIOS at the moment and I would > expect that TCG will likely not write one. Likely all vendors have moved > on to (U)EFI. We realized this also while implementing TPM 2 support for > SeaBIOS and I ended up reusing the ACPI TCPA table but adopted the EFI > specified log format with that special first entry. Can we accomodate that > ? Does that match to "SHA1 Event Log Entry Format" defined in [1]? In addition "Crypto Agile Log Entry Format" must be supported. Philip: what was the UEFI handover procedure that was discussed in TPM BoF at LSS 2016? > Stefan [1] http://www.trustedcomputinggroup.org/wp-content/uploads/EFI-Protocol-Specification-rev13-160330final.pdf /Jarkko ------------------------------------------------------------------------------