From: "Michael Niewöhner" <linux@mniewoehner.de>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
peterhuewe@gmx.de, jgg@ziepe.ca, arnd@arndb.de,
linux-integrity@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Nayna Jain <nayna@linux.ibm.com>,
Ken Goldman <kgold@linux.ibm.com>
Subject: Re: tpm_tis TPM2.0 not detected on cold boot
Date: Thu, 10 Jan 2019 19:00:28 +0100 [thread overview]
Message-ID: <3245408721bf1480f24af08db668fa7e3e7c848b.camel@mniewoehner.de> (raw)
In-Reply-To: <20190110171923.GC6589@linux.intel.com>
On Thu, 2019-01-10 at 19:19 +0200, Jarkko Sakkinen wrote:
> 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@debian:~# 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@debian:~# 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@debian:~# tpm_version
> > Tspi_Context_Connect failed: 0x00003011 - layer=tsp, code=0011 (17),
> > Communication failure
> > root@debian:~# 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@debian:~# 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
Right. I realized that too late... Have a look at my email from Fri, 04 Jan 2019
19:26:10 +0100
Michael
next prev parent reply other threads:[~2019-01-10 18:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 13:32 tpm_tis TPM2.0 not detected on cold boot Michael Niewöhner
2018-12-22 13:47 ` Michael Niewöhner
2018-12-22 22:53 ` Mimi Zohar
2018-12-23 11:55 ` Michael Niewöhner
2018-12-25 13:55 ` Michael Niewöhner
2018-12-30 3:33 ` Mimi Zohar
2018-12-30 13:22 ` Michael Niewöhner
2018-12-31 18:10 ` Ken Goldman
2018-12-31 21:17 ` Mimi Zohar
2019-01-01 16:15 ` Michael Niewöhner
2019-01-01 16:38 ` Mimi Zohar
2019-01-01 16:47 ` Michael Niewöhner
2018-12-31 17:56 ` Ken Goldman
2019-01-03 13:27 ` Jarkko Sakkinen
2019-01-03 13:38 ` Michael Niewöhner
2019-01-03 15:04 ` Jarkko Sakkinen
2019-01-03 15:47 ` Michael Niewöhner
2019-01-04 11:58 ` Michael Niewöhner
2019-01-04 15:28 ` Michael Niewöhner
2019-01-04 18:26 ` Michael Niewöhner
2019-01-10 17:28 ` Jarkko Sakkinen
2019-01-10 18:03 ` Michael Niewöhner
2019-01-10 17:19 ` Jarkko Sakkinen
2019-01-10 18:00 ` Michael Niewöhner [this message]
2019-01-03 13:41 ` Jarkko Sakkinen
2019-01-03 13:55 ` Michael Niewöhner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3245408721bf1480f24af08db668fa7e3e7c848b.camel@mniewoehner.de \
--to=linux@mniewoehner.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arnd@arndb.de \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=kgold@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nayna@linux.ibm.com \
--cc=peterhuewe@gmx.de \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).