Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1530506 > unrolled thread
| Started by | Jason Gunthorpe <jgunthorpe@obsidianresearch.com> |
|---|---|
| First post | 2016-11-25 20:50 +0100 |
| Last post | 2016-11-26 14:00 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v5 3/3] tpm: add securityfs support for TPM 2.0 firmware event log Jason Gunthorpe <jgunthorpe@obsidianresearch.com> - 2016-11-25 20:50 +0100
Re: [PATCH v5 3/3] tpm: add securityfs support for TPM 2.0 firmware event log Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> - 2016-11-26 14:00 +0100
| From | Jason Gunthorpe <jgunthorpe@obsidianresearch.com> |
|---|---|
| Date | 2016-11-25 20:50 +0100 |
| Subject | Re: [PATCH v5 3/3] tpm: add securityfs support for TPM 2.0 firmware event log |
| Message-ID | <sHuFr-4La-3@gated-at.bofh.it> |
On Thu, Nov 24, 2016 at 11:10:57PM +0200, Jarkko Sakkinen wrote: > On Wed, Nov 23, 2016 at 12:27:37PM -0500, Nayna Jain wrote: > > Unlike the device driver support for TPM 1.2, the TPM 2.0 does > > not support the securityfs pseudo files for displaying the > > firmware event log. > > > > This patch enables support for providing the TPM 2.0 event log in > > binary form. TPM 2.0 event log supports a crypto agile format that > > records multiple digests, which is different from TPM 1.2. This > > patch enables the tpm_bios_log_setup for TPM 2.0 and adds the > > event log parser which understand the TPM 2.0 crypto agile format. > > > > Signed-off-by: Nayna Jain <nayna@linux.vnet.ibm.com> > > I don't want to say much about this before I've tested it. I wonder > what cheap hardware I could use to test this. Any advice is on this > from anyone is much appreciated. If you found a small ARM system with TPM you could customize the uboot to build an event log and pass it in via DT. Not sure how much work that would be, does uboot have tpm code already? Jason
[toc] | [next] | [standalone]
| From | Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> |
|---|---|
| Date | 2016-11-26 14:00 +0100 |
| Message-ID | <sHKKe-6IQ-5@gated-at.bofh.it> |
| In reply to | #1530506 |
On Fri, Nov 25, 2016 at 12:43:17PM -0700, Jason Gunthorpe wrote: > On Thu, Nov 24, 2016 at 11:10:57PM +0200, Jarkko Sakkinen wrote: > > On Wed, Nov 23, 2016 at 12:27:37PM -0500, Nayna Jain wrote: > > > Unlike the device driver support for TPM 1.2, the TPM 2.0 does > > > not support the securityfs pseudo files for displaying the > > > firmware event log. > > > > > > This patch enables support for providing the TPM 2.0 event log in > > > binary form. TPM 2.0 event log supports a crypto agile format that > > > records multiple digests, which is different from TPM 1.2. This > > > patch enables the tpm_bios_log_setup for TPM 2.0 and adds the > > > event log parser which understand the TPM 2.0 crypto agile format. > > > > > > Signed-off-by: Nayna Jain <nayna@linux.vnet.ibm.com> > > > > I don't want to say much about this before I've tested it. I wonder > > what cheap hardware I could use to test this. Any advice is on this > > from anyone is much appreciated. > > If you found a small ARM system with TPM you could customize the uboot > to build an event log and pass it in via DT. > > Not sure how much work that would be, does uboot have tpm code > already? I have BeagleBoard Rev C (omap3530 arm board) and it has GPIOs but at the moment I do not possess a spare dTPM module. I'll ask my employer for one. It's quite old (2009), which is a good thing because of range of support I would presume... If I get the spare dTPM I can do I2C/SPI through GPIOs as long as I find a way to inject stuff to DT. Hmm.. that said I've never done this before. I guess you can ask I2C/SPI driver somehow to use GPIOs? > Jason /Jarkko
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web