All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 6 Sep 2018 13:02:43 +0300	[thread overview]
Message-ID: <20180906100243.GB27302@linux.intel.com> (raw)
In-Reply-To: <CAN19L9GiTJnzWMPXLpkRWW2WSAvZx2-x0Co=Tf=V_-dUf4q3OQ@mail.gmail.com>

On Wed, Sep 05, 2018 at 02:35:12PM -0300, Martin Galvan wrote:
> El mie., 5 sept. 2018 a las 14:32, Jarkko Sakkinen
> (<jarkko.sakkinen@linux.intel.com>) escribio:
> > Those files do not make sense because you can get the same information
> > by talking to /dev/tpm0.
> 
> Wouldn't that require using a lower-level interface, though? IIRC one
> of the reasons of tpm2-tools' existence is to provide a user-friendly
> way to do this. I was hoping there would be some way to do this
> without having to install tpm2-tools.

Would be trivial to write utilities that talk raw TPM 2.0 protocol and
give you equivalent information.

Some sample code from my smoke tests:

  https://github.com/jsakkine-intel/tpm2-scripts

I would write such utilities in raw C though but as you can see it is
not rocket science.

/Jarkko

  parent reply	other threads:[~2018-09-06 14:37 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
2018-09-05 17:35         ` Martin Galvan
2018-09-05 17:40           ` Peter Huewe
2018-09-06 10:02           ` Jarkko Sakkinen [this message]
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=20180906100243.GB27302@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.