On Wed, Mar 28, 2018 at 11:51:26AM -0400, Trevor Woerner wrote:
Wow, what a great time to come across this thread!
I also have been trying to use TPM on a RPi3 and was seeing the exact same
problems. I, however, was using OE and meta-measured to build my images. It
turns out that meta-measured/recipes-tpm/tpm2-tools wasn't DEPENDing on
tpm2-abrmd, so all builds as a result were not enabling the tabrmd TCTI.
By the way, what's the difference between "abrmd" and "tabrmd"?
There isn't one really. The daemon was named 'tpm2-abrmd' instead of
'tabrmd' based on some early user feedback. Having the 'tpm2' in the
name of the daemon made its purpose more clear according to this user.
'tabrmd' is the same name just with the 'tpm2' collapsed into the rest
of the acronym.
I can see where having an additional variation would cause confusion.
rather confusing that the tools list "tabrmd" as a TCTI, but in order to
use it one specifies "abrmd". Something feels wrong.
Being consistent is important especially w/r/t documentation. Seems like
a worthy bug for the tools issue tracker.
Also thanks for giving meta-measured some love. I've been neglecting it
a bit on account of work on the impending 2.0 release of the core TSS2
libraries. Once we ship the next major release of all components my plan
is to work on upstreaming the recipes to whatever OE layer is
appropriate to get them properly supported.
# tpm2_pcrlist -v
# tpm2_pcrlist -T tabrmd
ERROR: Unknown tcti, got: "tabrmd"
# tpm2_pcrlist -T abrmd
0 : 0000000000000000000000000000000000000000
1 : 0000000000000000000000000000000000000000
tpm2 mailing list