From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Martin Galvan <omgalvan.86@gmail.com>
Cc: jgg@ziepe.ca, linux-integrity@vger.kernel.org
Subject: Re: caps file showing wrong TCG version?
Date: Wed, 5 Sep 2018 20:32:23 +0300 [thread overview]
Message-ID: <20180905173223.GC11368@linux.intel.com> (raw)
In-Reply-To: <CAN19L9GnjOR6QCZp7M=v+PnBUS2WmbPzoDX9vHVunrdB_yQOUA@mail.gmail.com>
On Tue, Sep 04, 2018 at 06:55:45PM -0300, Martin Galvan wrote:
> El mar., 4 sept. 2018 a las 18:33, Jason Gunthorpe (<jgg@ziepe.ca>) escribio:
> > Recursive sounds bad.. what are you seeing?
>
> At least on my system, /sys/class/tpm/tpm0/device has a 'tpm' dir
> which seems to replicate the tpm0/device struct endlessly. Digging a
> bit deeper I see:
>
> $ ls -l /sys/class/tpm/tpm0/device
> lrwxrwxrwx 1 root root 0 Sep 4 12:15 /sys/class/tpm/tpm0/device ->
> ../../../00:09
>
> The 00:09 dir in turn refers to ls /sys/devices/pnp0/00:09.
>
> On an unrelated note: I was recently told that
> /sys/class/tpm/tpm0/caps doesn't exist for TPM 2.0. This is
> inconvenient, since the manufacturer and version info exposed through
> that file can be used to detect CVE-2017-15361. Is there an equivalent
> file for TPM 2.0?
Those files do not make sense because you can get the same information
by talking to /dev/tpm0.
/Jarkko
next prev parent reply other threads:[~2018-09-05 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 20:03 caps file showing wrong TCG version? Martin Galvan
2018-09-04 20:05 ` Martin Galvan
2018-09-04 20:27 ` Martin Galvan
2018-09-04 21:33 ` Jason Gunthorpe
2018-09-04 21:55 ` Martin Galvan
2018-09-05 17:32 ` Jarkko Sakkinen [this message]
2018-09-05 17:35 ` Martin Galvan
2018-09-05 17:40 ` Peter Huewe
2018-09-06 10:02 ` Jarkko Sakkinen
2018-09-05 17:30 ` Jarkko Sakkinen
2018-09-05 17:32 ` Martin Galvan
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=20180905173223.GC11368@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=omgalvan.86@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.