[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190110171923.GC6589@linux.intel.com>
Date: Thu, 10 Jan 2019 19:19:23 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Michael Niewöhner <linux@...ewoehner.de>
Cc: Mimi Zohar <zohar@...ux.ibm.com>,
James Bottomley <James.Bottomley@...senPartnership.com>,
peterhuewe@....de, jgg@...pe.ca, arnd@...db.de,
linux-integrity@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Nayna Jain <nayna@...ux.ibm.com>,
Ken Goldman <kgold@...ux.ibm.com>
Subject: Re: tpm_tis TPM2.0 not detected on cold boot
On Thu, Jan 03, 2019 at 04:47:31PM +0100, Michael Niewöhner wrote:
> On Thu, 2019-01-03 at 17:04 +0200, Jarkko Sakkinen wrote:
> > On Thu, Jan 03, 2019 at 02:38:11PM +0100, Michael Niewöhner wrote:
> > > On Thu, 2019-01-03 at 15:27 +0200, Jarkko Sakkinen wrote:
> > > > On Sun, Dec 23, 2018 at 12:55:12PM +0100, Michael Niewöhner wrote:
> > > > > There is another issue but I don't know if both are related. Maybe
> > > > > that's
> > > > > just a
> > > > > timing issue...
> > > > >
> > > > > root@...ian:~# dd if=/dev/hwrng bs=1 count=1
> > > > > dd: error reading '/dev/hwrng': Operation not permitted
> > > > > 0+0 records in
> > > > > 0+0 records out
> > > > > 0 bytes copied, 0.755958 s, 0.0 kB/s
> > > > > root@...ian:~# dd if=/dev/hwrng bs=1 count=1 | xxd; dd if=/dev/hwrng
> > > > > bs=1
> > > > > count=1 | xxd
> > > > > dd: error reading '/dev/hwrng': Operation not permitted
> > > > > 0+0 records in
> > > > > 0+0 records out
> > > > > 0 bytes copied, 0.755697 s, 0.0 kB/s
> > > > > 1+0 records in
> > > > > 1+0 records out
> > > > > 00000000: 52 R
> > > > > 1 byte copied, 0.0106268 s, 0.1 kB/s
> > > > >
> > > > >
> > > > > Michael
> > > >
> > > > What does /sys/devices/virtual/misc/hw_random/rng_current show?
> > > >
> > > > Did run commands as a sanity check on my laptop and seem to work.
> > > >
> > > > /Jarkko
> > >
> > > rng_current says "tpm-rng-0", which should be correct
> >
> > Is /dev/tpm0 accessible and usable?
> >
> > /Jarkko
>
> No, it does not seem to work:
>
> root@...ian:~# tpm_version
> Tspi_Context_Connect failed: 0x00003011 - layer=tsp, code=0011 (17),
> Communication failure
> root@...ian:~# tcsd -f
> TCSD TDDL ioctl: (25) Inappropriate ioctl for device
> TCSD TDDL Falling back to Read/Write device support.
> TCSD TDDL ERROR: write to device /dev/tpm0 failed: Operation not permitted
> TCSD TCS ERROR: TCS GetCapability failed with result = 0x1087
> root@...ian:~# stat /dev/tpm0
> File: /dev/tpm0
> Size: 0 Blocks: 0 IO Block: 4096 character special
> file
> Device: 6h/6d Inode: 1114 Links: 1 Device type: a,e0
> Access: (0600/crw-------) Uid: ( 104/ tss) Gid: ( 112/ tss)
> Access: 2019-01-03 16:39:20.627635333 +0100
> Modify: 2019-01-03 16:39:20.627635333 +0100
> Change: 2019-01-03 16:39:20.627635333 +0100
> Birth: -
But those tools should not work because TrouSerS is for TPM 1.2.
/Jarkko
Powered by blists - more mailing lists