10:07 p.m.
Hey there madprops,
On Sun, Mar 18, 2018 at 02:04:15PM +0100, madprops(a)gmx.net wrote:
<html><head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8"></head><body><div style="font-family:
Verdana;font-size: 12.0px;"><div>
<div class="signature">
<div class="signature">
<div>I'm trying to get an "Infineon Iridium SLB 9670 TPM 2.0 SPI
Board" run on my Raspberry Pi 3. I have downloaded, compiled and installed the
latest versions of tpm2-abrmd, tpm2-tss and tpm2-tools. I started tpm2-abrmd as root,
hoping that I can then interact with the Infineon TPM using tpm2-tools.
"tpm2_pcrlist" and all other tpm2_* commands, however, return error
"ERROR: Failed to initialize tcti context: 0x1".</div>
Can you please provide some more info about your configuration?
Specifically:
- the version of the TSS2 libraries you're using
- the version of the tabrmd you're using
- the configuration options you're passing to each
A log file from the tabrmd with logging dialed all the way up would be
helpful. Since tabrmd uses glib and it's logging infrastructure you dial
up the debug output all the way by setting `G_MESSAGES_DEBUG=all` in the
daemon's environment.
<div> </div>
<div>Any ideas? Thanks!</div>
The most common issue we've seen people run into when installing from
source is that the default value for the `prefix` and some other
installation directories aren't what most expect.
Still, if you're running the daemon as root you shouldn't have any
issues w/r to permissions on the /dev/tpm0 device node so I wonder if
this node even exists on your platform. You may want to check to see if
`/dev/tpm0` is even present on your system. You're on an ARM platform
which means the kernel will only be aware of the TPM2 device you've
added if you configure the device tree properly.
Regards,
Philip
<div>pi@raspberrypi:~/TPM/tpm2-abrmd $ uname -a<br>
Linux raspberrypi 4.4.50-v7+ #1 SMP Wed Mar 14 14:01:00 PDT 2018 armv7l GNU/Linux
(<== includes patch provided by Infineon)</div>
<div> </div>
<div>pi@raspberrypi:~/TPM/tpm2-abrmd $ dmesg | grep tpm<br>
[ 3.700384] tpm_spi_tis spi0.1: 2.0 TPM (device-id 0xB6BC,
rev-id 16)</div>
<div> </div>
<div>pi@raspberrypi:/etc $ cat /etc/os-release<br>
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"<br>
NAME="Raspbian GNU/Linux"<br>
VERSION_ID="9"<br>
VERSION="9 (stretch)"<br>
ID=raspbian<br>
ID_LIKE=debian<br>
HOME_URL="http://www.raspbian.org/"<br>
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"<...
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"&l...
</div>
</div>
</div></div></body></html>
_______________________________________________
tpm2 mailing list
tpm2(a)lists.01.org
https://lists.01.org/mailman/listinfo/tpm2
3:49 a.m.
On 03/19/2018 06:07 AM, Philip Tricca wrote:
Hey there madprops,
On Sun, Mar 18, 2018 at 02:04:15PM +0100, madprops(a)gmx.net wrote:
> <html><head>
> <meta http-equiv="Content-Type" content="text/html;
charset=utf-8"></head><body><div style="font-family:
Verdana;font-size: 12.0px;"><div>
> <div class="signature">
> <div class="signature">
> <div>I'm trying to get an "Infineon Iridium SLB 9670 TPM 2.0 SPI
Board" run on my Raspberry Pi 3. I have downloaded, compiled and installed the
latest versions of tpm2-abrmd, tpm2-tss and tpm2-tools. I started tpm2-abrmd as root,
hoping that I can then interact with the Infineon TPM using tpm2-tools.
"tpm2_pcrlist" and all other tpm2_* commands, however, return error
"ERROR: Failed to initialize tcti context: 0x1".</div>
>
Can you please provide some more info about your configuration?
Specifically:
- the version of the TSS2 libraries you're using
- the version of the tabrmd you're using
- the configuration options you're passing to each
A log file from the tabrmd with logging dialed all the way up would be
helpful. Since tabrmd uses glib and it's logging infrastructure you dial
up the debug output all the way by setting `G_MESSAGES_DEBUG=all` in the
daemon's environment.
> <div> </div>
>
> <div>Any ideas? Thanks!</div>
The most common issue we've seen people run into when installing from
source is that the default value for the `prefix` and some other
installation directories aren't what most expect.
Still, if you're running the daemon as root you shouldn't have any
issues w/r to permissions on the /dev/tpm0 device node so I wonder if
this node even exists on your platform. You may want to check to see if
`/dev/tpm0` is even present on your system. You're on an ARM platform
which means the kernel will only be aware of the TPM2 device you've
added if you configure the device tree properly.
Regards,
Philip
We should probably add a FAQ to the tpm2-{tss,abrmd,tools} projects, since
the same questions are being repeated over and over in the mailing list.
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat
8:31 a.m.
On Mon, Mar 19, 2018 at 11:49:45AM +0100, Javier Martinez Canillas wrote:
On 03/19/2018 06:07 AM, Philip Tricca wrote:
> Hey there madprops,
>
> On Sun, Mar 18, 2018 at 02:04:15PM +0100, madprops(a)gmx.net wrote:
>> <html><head>
>> <meta http-equiv="Content-Type" content="text/html;
charset=utf-8"></head><body><div style="font-family:
Verdana;font-size: 12.0px;"><div>
>> <div class="signature">
>> <div class="signature">
>> <div>I'm trying to get an "Infineon Iridium SLB 9670 TPM 2.0
SPI Board" run on my Raspberry Pi 3. I have downloaded, compiled and installed
the latest versions of tpm2-abrmd, tpm2-tss and tpm2-tools. I started tpm2-abrmd as root,
hoping that I can then interact with the Infineon TPM using tpm2-tools.
"tpm2_pcrlist" and all other tpm2_* commands, however, return error
"ERROR: Failed to initialize tcti context: 0x1".</div>
>>
>
> Can you please provide some more info about your configuration?
> Specifically:
> - the version of the TSS2 libraries you're using
> - the version of the tabrmd you're using
> - the configuration options you're passing to each
>
> A log file from the tabrmd with logging dialed all the way up would be
> helpful. Since tabrmd uses glib and it's logging infrastructure you dial
> up the debug output all the way by setting `G_MESSAGES_DEBUG=all` in the
> daemon's environment.
>
>> <div> </div>
>>
>> <div>Any ideas? Thanks!</div>
>
> The most common issue we've seen people run into when installing from
> source is that the default value for the `prefix` and some other
> installation directories aren't what most expect.
>
> Still, if you're running the daemon as root you shouldn't have any
> issues w/r to permissions on the /dev/tpm0 device node so I wonder if
> this node even exists on your platform. You may want to check to see if
> `/dev/tpm0` is even present on your system. You're on an ARM platform
> which means the kernel will only be aware of the TPM2 device you've
> added if you configure the device tree properly.
>
> Regards,
> Philip
>
We should probably add a FAQ to the tpm2-{tss,abrmd,tools} projects, since
the same questions are being repeated over and over in the mailing list.
No doubt. The first bit about providing additional data in bug reports /
questions should probably land in the CONTRIBUTING.md files. A FAQ on
the right wikis would be a good thing as well.
With the churn in the TSS2 libs dying down I'll be refocusing on the
tabrmd so I'll probably start there. If you've got the cycles and the
motivation feel free to jump on the wiki and start adding content.
Philip
12:19 p.m.
Hey madprops,
Thanks for the additional data.
On Mon, Mar 19, 2018 at 09:17:33PM +0100, madprops(a)gmx.net wrote:
<html><head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8"></head><body><div style="font-family:
Verdana;font-size: 12.0px;"><div>
<div>Thank you, Philip! I meanwhile noticed the tools work when I stop tpm2-abrmd
and connect directly to the TPM: </div>
Well this debunks my theory that your issue was down in the dev tree :)
<div> </div>
<div>pi@raspberrypi:~ $ sudo tpm2_pcrlist -T device:/dev/tpm0<br>
sha1 :<br>
0 : 0000000000000000000000000000000000000000<br>
1 : 0000000000000000000000000000000000000000<br>
[...]</div>
<div> </div>
<div>Please find below the information you asked for. While tpm2-abrmd is running
(as root) I still get this:</div>
<div> </div>
<div>pi@raspberrypi:~ $ tpm2_pcrlist<br>
ERROR: Failed to initialize tcti context: 0x1</div>
Seeing this error while the tabrmd is running, but having the tools
execute successfully with it stopped is a big hint. This indicates
that the tools are probably trying to connect to the /dev/tpm0 device
node directly instead of using the tabrmd.
I've only see this happen if / when the tools are built in advance of
building *and* installing the tabrmd. This happens because the tools
build looks for the installed TCTI library for communicating with the
daemon. If it doesn't find this library then the tools can't be linked
against it and the build will fall back to using the device TCTI as
the default. The `config.log` file in the tools build has the output
from the `configure` script and this will tell you which TCTI modules
are enabled / disabled.
Another way to check this theory is to take one of the tools executables
and use `readelf` to dump information about the libraries that it links
to. If the tabrmd TCTI library isn't listed then something it up.
Everything else below looks right.
Regards,
Philip
<div> </div>
<div>pi@raspberrypi:~ $ export TPM2TOOLS_TCTI_NAME=tabrmd<br>
pi@raspberrypi:~ $ tpm2_pcrlist<br>
ERROR: Unknown tcti, got: "tabrmd"</div>
<div> </div>
<div>======== Versions:</div>
<div>tpm2-abrmd: 1.3.1_rc0<br>
tpm2-tools: 3.0.3<br>
tpm2-tss: 1.4.0</div>
<div> </div>
<div>======== /dev/tpm0</div>
<div>pi@raspberrypi:~ $ ls -la /dev/tpm0<br>
crw------- 1 root root 10, 224 Mar 17 21:35 /dev/tpm0</div>
<div>======== tpm2-abrmd LOG</div>
<div>root@raspberrypi:/home/pi# tpm2-abrmd<br>
** INFO: tabrmd startup<br>
** (process:1852): DEBUG: tcti_factory_set_property<br>
** (process:1852): DEBUG: PROP_TCTI_TYPE<br>
** (process:1852): DEBUG: value: 0x1<br>
** (process:1852): DEBUG: tcti_factory_set_property<br>
** (process:1852): DEBUG: TctiFactory set device_name: /dev/tpm0<br>
** (process:1852): DEBUG: tcti_factory_set_property<br>
** (process:1852): DEBUG: TctiFactory set socket_address: 127.0.0.1<br>
** (process:1852): DEBUG: tcti_factory_set_property<br>
** (process:1852): DEBUG: TctiFactory set socket_port: 2321<br>
** INFO: logging to stdout<br>
** (tpm2-abrmd:1852): DEBUG: tcti_factory_get_tcti<br>
** (tpm2-abrmd:1852): DEBUG: TctiDevice set filename: /dev/tpm0<br>
** INFO: entering g_main_loop<br>
** INFO: init_thread_func start<br>
** (tpm2-abrmd:1852): DEBUG: random_class_init<br>
** (tpm2-abrmd:1852): DEBUG: opening entropy source: /dev/urandom<br>
** (tpm2-abrmd:1852): DEBUG: reading from entropy source: /dev/urandom<br>
** (tpm2-abrmd:1852): DEBUG: seeding rand with -1263045295<br>
** (tpm2-abrmd:1852): DEBUG: connection_manager_set_property: 0x15c5ef0<br>
** (tpm2-abrmd:1852): DEBUG: max_connections: 0x1b<br>
** (tpm2-abrmd:1852): DEBUG: ConnectionManager: 0x15c5ef0<br>
** (tpm2-abrmd:1852): DEBUG: IpcFrontendDbus set bus_name:
com.intel.tss2.Tabrmd<br>
** (tpm2-abrmd:1852): DEBUG: ipc_frontend_connect: 0x75b01a08<br>
** (tpm2-abrmd:1852): DEBUG: tcti_initialize: 0x15c5200<br>
** (tpm2-abrmd:1852): DEBUG: sapi_context_init w/ Tcti: 0x15c5200<br>
** (tpm2-abrmd:1852): DEBUG: tcti_peek_context: 0x15c5200<br>
** (tpm2-abrmd:1852): DEBUG: Allocating 0x1040 bytes for SAPI context<br>
** (tpm2-abrmd:1852): DEBUG: access_broker_set_property: 0x75b0b720<br>
** (tpm2-abrmd:1852): DEBUG: sapi_context: 0x75b0a690<br>
** (tpm2-abrmd:1852): DEBUG: access_broker_set_property: 0x75b0b720<br>
** (tpm2-abrmd:1852): DEBUG: tcti: 0x15c5200<br>
** (tpm2-abrmd:1852): DEBUG: created AccessBroker: 0x75b0b720<br>
** (tpm2-abrmd:1852): DEBUG: access_broker_init_tpm: 0x75b0b720<br>
** INFO: on_bus_acquired: com.intel.tss2.Tabrmd<br>
** INFO: on_name_acquired: com.intel.tss2.Tabrmd<br>
** (tpm2-abrmd:1852): DEBUG: Got proxy object for DBus daemon.<br>
** (tpm2-abrmd:1852): DEBUG: access_broker_get_tpm_properties_fixed<br>
** (tpm2-abrmd:1852): DEBUG: command_attrs_class_init<br>
** (tpm2-abrmd:1852): DEBUG: created CommandAttrs: 0x75b01260<br>
** (tpm2-abrmd:1852): DEBUG: GetCapabilty for 0x500 commands<br>
** (tpm2-abrmd:1852): DEBUG: got attributes for 0x5a commands<br>
** (tpm2-abrmd:1852): DEBUG: command_source_class_init<br>
** (tpm2-abrmd:1852): DEBUG: command_source_set_properties: 0x75b02c50<br>
** (tpm2-abrmd:1852): DEBUG: command_attrs: 0x75b01260<br>
** (tpm2-abrmd:1852): DEBUG: command_source_set_properties: 0x75b02c50<br>
** (tpm2-abrmd:1852): DEBUG: created command source: 0x75b02c50<br>
** (tpm2-abrmd:1852): DEBUG: session_list_new with max-per-connection: 0x4<br>
** (tpm2-abrmd:1852): DEBUG: session_list_init<br>
** (tpm2-abrmd:1852): DEBUG: session_list_set_property: 0x15c5fb0 max-per-connection:
4<br>
** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property: 0x75b02ca0<br>
** (tpm2-abrmd:1852): DEBUG: in_queue: 0x75b00f90<br>
** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property: 0x75b02ca0<br>
** (tpm2-abrmd:1852): DEBUG: access_broker: 0x75b0b720<br>
** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property: 0x75b02ca0<br>
** (tpm2-abrmd:1852): DEBUG: created ResourceManager: 0x75b02ca0<br>
** (tpm2-abrmd:1852): DEBUG: response_sink_set_property<br>
** (tpm2-abrmd:1852): DEBUG: setting PROP_IN_QUEUE<br>
** (tpm2-abrmd:1852): DEBUG: created response source: 0x75b012a8<br>
** (tpm2-abrmd:1852): DEBUG: source_add_sink<br>
** (tpm2-abrmd:1852): DEBUG: command_soruce_add_sink: CommandSource: 0x75b02c50 , Sink:
0x75b02ca0<br>
** (tpm2-abrmd:1852): DEBUG: command_source_set_properties: 0x75b02c50<br>
** (tpm2-abrmd:1852): DEBUG: sink: 0x75b02ca0<br>
** (tpm2-abrmd:1852): DEBUG: source_add_sink<br>
** (tpm2-abrmd:1852): DEBUG: resource_manager_add_sink: ResourceManager: 0x75b02ca0,
Sink: 0x75b012a8<br>
** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property: 0x75b02ca0<br>
** (tpm2-abrmd:1852): DEBUG: sink: 0x75b012a8<br>
** INFO: init_thread_func done<br>
** (tpm2-abrmd:1852): DEBUG: resource_manager_thread start<br>
** (tpm2-abrmd:1852): DEBUG: response_sink_thread blocking on input queue:
0x75b00e50<br>
** (tpm2-abrmd:1852): DEBUG: message_queue_dequeue 0x75b00e50<br>
** (tpm2-abrmd:1852): DEBUG: message_queue_dequeue 0x75b00f90</div>
<div> </div>
<div>======== MISC</div>
<div>pi@raspberrypi:~/TPM/tpm2-tss $ cat
/etc/dbus-1/system.d/tpm2-abrmd.conf<br>
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration
1.0//EN"<br>
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"><br>
<busconfig><br>
<!-- ../system.conf have denied everything, so we just punch some holes
--><br>
<policy user="tss"><br>
<allow
own="com.intel.tss2.Tabrmd"/><br>
</policy><br>
<policy user="root"><br>
<allow
own="com.intel.tss2.Tabrmd"/><br>
</policy><br>
<policy context="default"><br>
<allow
send_destination="com.intel.tss2.Tabrmd"/><br>
<allow
receive_sender="com.intel.tss2.Tabrmd"/><br>
</policy><br>
</busconfig></div>
<div> </div>
<div> </div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px
10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;">
<div style="margin:0 0 10px
0;"><b>Gesendet:</b> Montag, 19. März 2018 um 06:07
Uhr<br>
<b>Von:</b> "Philip Tricca"
&lt;philip.b.tricca(a)intel.com&gt;<br>
<b>An:</b> madprops@gmx.net<br>
<b>Cc:</b> tpm2@lists.01.org<br>
<b>Betreff:</b> Re: [tpm2] Problem with Infineon Iridium SLB 9670
TPM2.0</div>
<div name="quoted-content">Hey there madprops,<br>
<br>
On Sun, Mar 18, 2018 at 02:04:15PM +0100, madprops(a)gmx.net wrote:<br>
> <html><head><br>
> <meta http-equiv="Content-Type"
content="text/html;
charset=utf-8"></head><body><div
style="font-family: Verdana;font-size:
12.0px;"><div><br>
> <div class="signature"><br>
> <div class="signature"><br>
> <div>I'm trying to get an &quot;Infineon Iridium SLB
9670 TPM 2.0 SPI Board&quot; run on my Raspberry Pi 3. I have downloaded, compiled
and installed the latest versions of tpm2-abrmd, tpm2-tss and tpm2-tools. I started
tpm2-abrmd as root, hoping that I can then interact with the Infineon TPM using
tpm2-tools. &quot;tpm2_pcrlist&quot; and all other tpm2_* commands,
however, return error &quot;ERROR: Failed to initialize tcti context:
0x1&quot;.</div><br>
><br>
<br>
Can you please provide some more info about your configuration?<br>
Specifically:<br>
- the version of the TSS2 libraries you're using<br>
- the version of the tabrmd you're using<br>
- the configuration options you're passing to each<br>
<br>
A log file from the tabrmd with logging dialed all the way up would be<br>
helpful. Since tabrmd uses glib and it's logging infrastructure you dial<br>
up the debug output all the way by setting `G_MESSAGES_DEBUG=all` in the<br>
daemon's environment.<br>
<br>
> <div>&nbsp;</div><br>
><br>
> <div>Any ideas? Thanks!</div><br>
<br>
The most common issue we've seen people run into when installing from<br>
source is that the default value for the `prefix` and some other<br>
installation directories aren't what most expect.<br>
<br>
Still, if you're running the daemon as root you shouldn't have any<br>
issues w/r to permissions on the /dev/tpm0 device node so I wonder if<br>
this node even exists on your platform. You may want to check to see if<br>
`/dev/tpm0` is even present on your system. You're on an ARM platform<br>
which means the kernel will only be aware of the TPM2 device you've<br>
added if you configure the device tree properly.<br>
<br>
Regards,<br>
Philip<br>
<br>
> <div>pi@raspberrypi:~/TPM/tpm2-abrmd $ uname
-a<br><br>
> Linux raspberrypi 4.4.50-v7&#43; #1 SMP Wed Mar 14 14:01:00 PDT 2018
armv7l GNU/Linux (&lt;== includes patch provided by
Infineon)</div><br>
><br>
> <div>&nbsp;</div><br>
><br>
> <div>pi@raspberrypi:~/TPM/tpm2-abrmd $ dmesg | grep
tpm<br><br>
> [&nbsp;&nbsp;&nbsp; 3.700384] tpm_spi_tis spi0.1: 2.0
TPM (device-id 0xB6BC, rev-id 16)</div><br>
><br>
> <div>&nbsp;</div><br>
><br>
> <div>pi@raspberrypi:/etc $ cat
/etc/os-release<br><br>
> PRETTY_NAME=&quot;Raspbian GNU/Linux 9
(stretch)&quot;<br><br>
> NAME=&quot;Raspbian GNU/Linux&quot;<br><br>
> VERSION_ID=&quot;9&quot;<br><br>
> VERSION=&quot;9 (stretch)&quot;<br><br>
> ID=raspbian<br><br>
> ID_LIKE=debian<br><br>
> HOME_URL=&quot;<a
href="http://www.raspbian.org/&quot"
target="_blank">http://www.raspbian.org/&quot</a&...
> SUPPORT_URL=&quot;<a
href="http://www.raspbian.org/RaspbianForums&quot"
target="_blank">http://www.raspbian.org/RaspbianForums&a...
> BUG_REPORT_URL=&quot;<a
href="http://www.raspbian.org/RaspbianBugs&quot"
target="_blank">http://www.raspbian.org/RaspbianBugs&...
> </div><br>
> </div><br>
>
</div></div></body></html><br>
<br>
> _______________________________________________<br>
> tpm2 mailing list<br>
> tpm2(a)lists.01.org<br>
> <a href="https://lists.01.org/mailman/listinfo/tpm2"
target="_blank">https://lists.01.org/mailman/listinfo/tpm2&l...
</div>
</div>
</div>
</div>
<div> </div>
<div
class="signature"> </div></div></body></html>
12:58 p.m.
-----Original Message-----
From: tpm2 [mailto:tpm2-bounces@lists.01.org] On Behalf Of Philip Tricca
Sent: Tuesday, March 20, 2018 12:20 PM
To: madprops(a)gmx.net
Cc: tpm2(a)lists.01.org
Subject: Re: [tpm2] Problem with Infineon Iridium SLB 9670 TPM2.0
Hey madprops,
Thanks for the additional data.
On Mon, Mar 19, 2018 at 09:17:33PM +0100, madprops(a)gmx.net wrote:
> <html><head>
> <meta http-equiv="Content-Type" content="text/html;
> charset=utf-8"></head><body><div style="font-family:
> Verdana;font-size: 12.0px;"><div> <div>Thank you, Philip! I
meanwhile
> noticed the tools work when I stop tpm2-abrmd and connect directly to
> the TPM: </div>
Well this debunks my theory that your issue was down in the dev tree :)
> <div> </div>
>
> <div>pi@raspberrypi:~ $ sudo tpm2_pcrlist -T device:/dev/tpm0<br>
> sha1 :<br>
> 0 : 0000000000000000000000000000000000000000<br>
> 1 : 0000000000000000000000000000000000000000<br>
> [...]</div>
>
> <div> </div>
>
> <div>Please find below the information you asked for. While tpm2-abrmd
> is running (as root) I still get this:</div>
>
> <div> </div>
>
> <div>pi@raspberrypi:~ $ tpm2_pcrlist<br>
> ERROR: Failed to initialize tcti context: 0x1</div>
Seeing this error while the tabrmd is running, but having the tools execute
successfully with it stopped is a big hint. This indicates that the tools are probably
trying to connect to the /dev/tpm0 device node directly instead of using the
tabrmd.
I've only see this happen if / when the tools are built in advance of building *and*
installing the tabrmd. This happens because the tools build looks for the installed
TCTI library for communicating with the daemon. If it doesn't find this library then
the tools can't be linked against it and the build will fall back to using the
device
TCTI as the default. The `config.log` file in the tools build has the output from the
`configure` script and this will tell you which TCTI modules are enabled / disabled.
Another way to check this theory is to take one of the tools executables and use
`readelf` to dump information about the libraries that it links to. If the tabrmd
TCTI library isn't listed then something it up.
You can also specify -v to your tool commands option list to see what tcti's it
supports.
The first tcti in the string is the default IIC. I should have had an additional field
for default.
On master, we switched to dynamic TCTIs with abrmd always being the default.
I think the 4.0 release, I'm going to add a field to explicitly say what the default
Is.
Everything else below looks right.
Regards,
Philip
> <div> </div>
>
> <div>pi@raspberrypi:~ $ export TPM2TOOLS_TCTI_NAME=tabrmd<br>
> pi@raspberrypi:~ $ tpm2_pcrlist<br>
> ERROR: Unknown tcti, got: "tabrmd"</div>
>
> <div> </div>
>
> <div>======== Versions:</div>
>
> <div>tpm2-abrmd: 1.3.1_rc0<br>
> tpm2-tools: 3.0.3<br>
> tpm2-tss: 1.4.0</div>
>
> <div> </div>
>
> <div>======== /dev/tpm0</div>
>
> <div>pi@raspberrypi:~ $ ls -la /dev/tpm0<br>
> crw------- 1 root root 10, 224 Mar 17 21:35 /dev/tpm0</div>
>
> <div>======== tpm2-abrmd LOG</div>
>
> <div>root@raspberrypi:/home/pi# tpm2-abrmd<br>
> ** INFO: tabrmd startup<br>
> ** (process:1852): DEBUG: tcti_factory_set_property<br>
> ** (process:1852): DEBUG: PROP_TCTI_TYPE<br>
> ** (process:1852): DEBUG: value: 0x1<br>
> ** (process:1852): DEBUG: tcti_factory_set_property<br>
> ** (process:1852): DEBUG: TctiFactory set device_name: /dev/tpm0<br>
> ** (process:1852): DEBUG: tcti_factory_set_property<br>
> ** (process:1852): DEBUG: TctiFactory set socket_address:
> 127.0.0.1<br>
> ** (process:1852): DEBUG: tcti_factory_set_property<br>
> ** (process:1852): DEBUG: TctiFactory set socket_port: 2321<br>
> ** INFO: logging to stdout<br>
> ** (tpm2-abrmd:1852): DEBUG: tcti_factory_get_tcti<br>
> ** (tpm2-abrmd:1852): DEBUG: TctiDevice set filename: /dev/tpm0<br>
> ** INFO: entering g_main_loop<br>
> ** INFO: init_thread_func start<br>
> ** (tpm2-abrmd:1852): DEBUG: random_class_init<br>
> ** (tpm2-abrmd:1852): DEBUG: opening entropy source: /dev/urandom<br>
> ** (tpm2-abrmd:1852): DEBUG: reading from entropy source:
> /dev/urandom<br>
> ** (tpm2-abrmd:1852): DEBUG: seeding rand with -1263045295<br>
> ** (tpm2-abrmd:1852): DEBUG: connection_manager_set_property:
> 0x15c5ef0<br>
> ** (tpm2-abrmd:1852): DEBUG: max_connections: 0x1b<br>
> ** (tpm2-abrmd:1852): DEBUG: ConnectionManager: 0x15c5ef0<br>
> ** (tpm2-abrmd:1852): DEBUG: IpcFrontendDbus set bus_name:
> com.intel.tss2.Tabrmd<br>
> ** (tpm2-abrmd:1852): DEBUG: ipc_frontend_connect: 0x75b01a08<br>
> ** (tpm2-abrmd:1852): DEBUG: tcti_initialize: 0x15c5200<br>
> ** (tpm2-abrmd:1852): DEBUG: sapi_context_init w/ Tcti: 0x15c5200<br>
> ** (tpm2-abrmd:1852): DEBUG: tcti_peek_context: 0x15c5200<br>
> ** (tpm2-abrmd:1852): DEBUG: Allocating 0x1040 bytes for SAPI
> context<br>
> ** (tpm2-abrmd:1852): DEBUG: access_broker_set_property:
> 0x75b0b720<br>
> ** (tpm2-abrmd:1852): DEBUG: sapi_context: 0x75b0a690<br>
> ** (tpm2-abrmd:1852): DEBUG: access_broker_set_property:
> 0x75b0b720<br>
> ** (tpm2-abrmd:1852): DEBUG: tcti: 0x15c5200<br>
> ** (tpm2-abrmd:1852): DEBUG: created AccessBroker: 0x75b0b720<br>
> ** (tpm2-abrmd:1852): DEBUG: access_broker_init_tpm: 0x75b0b720<br>
> ** INFO: on_bus_acquired: com.intel.tss2.Tabrmd<br>
> ** INFO: on_name_acquired: com.intel.tss2.Tabrmd<br>
> ** (tpm2-abrmd:1852): DEBUG: Got proxy object for DBus daemon.<br>
> ** (tpm2-abrmd:1852): DEBUG:
> access_broker_get_tpm_properties_fixed<br>
> ** (tpm2-abrmd:1852): DEBUG: command_attrs_class_init<br>
> ** (tpm2-abrmd:1852): DEBUG: created CommandAttrs: 0x75b01260<br>
> ** (tpm2-abrmd:1852): DEBUG: GetCapabilty for 0x500 commands<br>
> ** (tpm2-abrmd:1852): DEBUG: got attributes for 0x5a commands<br>
> ** (tpm2-abrmd:1852): DEBUG: command_source_class_init<br>
> ** (tpm2-abrmd:1852): DEBUG: command_source_set_properties:
> 0x75b02c50<br>
> ** (tpm2-abrmd:1852): DEBUG: command_attrs:
0x75b01260<br>
> ** (tpm2-abrmd:1852): DEBUG: command_source_set_properties:
> 0x75b02c50<br>
> ** (tpm2-abrmd:1852): DEBUG: created command source: 0x75b02c50<br>
> ** (tpm2-abrmd:1852): DEBUG: session_list_new with max-per-connection:
> 0x4<br>
> ** (tpm2-abrmd:1852): DEBUG: session_list_init<br>
> ** (tpm2-abrmd:1852): DEBUG: session_list_set_property: 0x15c5fb0
> max-per-connection: 4<br>
> ** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property:
> 0x75b02ca0<br>
> ** (tpm2-abrmd:1852): DEBUG: in_queue: 0x75b00f90<br>
> ** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property:
> 0x75b02ca0<br>
> ** (tpm2-abrmd:1852): DEBUG: access_broker:
0x75b0b720<br>
> ** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property:
> 0x75b02ca0<br>
> ** (tpm2-abrmd:1852): DEBUG: created ResourceManager: 0x75b02ca0<br>
> ** (tpm2-abrmd:1852): DEBUG: response_sink_set_property<br>
> ** (tpm2-abrmd:1852): DEBUG: setting PROP_IN_QUEUE<br>
> ** (tpm2-abrmd:1852): DEBUG: created response source: 0x75b012a8<br>
> ** (tpm2-abrmd:1852): DEBUG: source_add_sink<br>
> ** (tpm2-abrmd:1852): DEBUG: command_soruce_add_sink: CommandSource:
> 0x75b02c50 , Sink: 0x75b02ca0<br>
> ** (tpm2-abrmd:1852): DEBUG: command_source_set_properties:
> 0x75b02c50<br>
> ** (tpm2-abrmd:1852): DEBUG: sink: 0x75b02ca0<br>
> ** (tpm2-abrmd:1852): DEBUG: source_add_sink<br>
> ** (tpm2-abrmd:1852): DEBUG: resource_manager_add_sink:
> ResourceManager: 0x75b02ca0, Sink: 0x75b012a8<br>
> ** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property:
> 0x75b02ca0<br>
> ** (tpm2-abrmd:1852): DEBUG: sink: 0x75b012a8<br>
> ** INFO: init_thread_func done<br>
> ** (tpm2-abrmd:1852): DEBUG: resource_manager_thread start<br>
> ** (tpm2-abrmd:1852): DEBUG: response_sink_thread blocking on input
> queue: 0x75b00e50<br>
> ** (tpm2-abrmd:1852): DEBUG: message_queue_dequeue 0x75b00e50<br>
> ** (tpm2-abrmd:1852): DEBUG: message_queue_dequeue 0x75b00f90</div>
>
> <div> </div>
>
> <div>======== MISC</div>
>
> <div>pi@raspberrypi:~/TPM/tpm2-tss $ cat
> /etc/dbus-1/system.d/tpm2-abrmd.conf<br>
> <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus
> Configuration 1.0//EN"<br>
> "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dt
> d"><br>
> <busconfig><br>
> <!-- ../system.conf have denied everything, so we just punch
> some holes --><br> <policy
user="tss"><br>
> <allow
> own="com.intel.tss2.Tabrmd"/><br>
> </policy><br>
> <policy user="root"><br>
> <allow own="com.intel.tss2.Tabrmd"/><br>
> </policy><br>
> <policy context="default"><br>
> <allow
> send_destination="com.intel.tss2.Tabrmd"/><br>
> <allow
> receive_sender="com.intel.tss2.Tabrmd"/><br>
> </policy><br>
> </busconfig></div>
>
> <div> </div>
>
> <div> </div>
>
> <div>
> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px
0
> 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word;
> -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
> <div style="margin:0 0 10px
0;"><b>Gesendet:</b> Montag, 19. März
> 2018 um 06:07 Uhr<br> <b>Von:</b> "Philip
Tricca"
> &lt;philip.b.tricca(a)intel.com&gt;<br>
> <b>An:</b> madprops@gmx.net<br>
> <b>Cc:</b> tpm2@lists.01.org<br>
> <b>Betreff:</b> Re: [tpm2] Problem with Infineon Iridium SLB
9670
> TPM2.0</div>
>
> <div name="quoted-content">Hey there madprops,<br> <br>
On Sun, Mar
> 18, 2018 at 02:04:15PM +0100, madprops(a)gmx.net wrote:<br> >
> <html><head><br> > <meta
> http-equiv="Content-Type" content="text/html;
> charset=utf-8"></head><body><div
> style="font-family: Verdana;font-size:
> 12.0px;"><div><br> > <div
> class="signature"><br>
> > <div class="signature"><br>
> > <div>I'm trying to get an &quot;Infineon Iridium
SLB
> 9670 TPM 2.0 SPI Board&quot; run on my Raspberry Pi 3. I have
> downloaded, compiled and installed the latest versions of tpm2-abrmd,
> tpm2-tss and tpm2-tools. I started tpm2-abrmd as root, hoping that I
> can then interact with the Infineon TPM using tpm2-tools.
> &quot;tpm2_pcrlist&quot; and all other tpm2_* commands,
> however, return error &quot;ERROR: Failed to initialize tcti
> context: 0x1&quot;.</div><br> ><br>
<br> Can you please
> provide some more info about your configuration?<br> Specifically:<br>
> - the version of the TSS2 libraries you're using<br>
> - the version of the tabrmd you're using<br>
> - the configuration options you're passing to each<br> <br> A log
file
> from the tabrmd with logging dialed all the way up would be<br>
> helpful. Since tabrmd uses glib and it's logging infrastructure you
> dial<br> up the debug output all the way by setting
> `G_MESSAGES_DEBUG=all` in the<br> daemon's environment.<br>
<br> >
> <div>&nbsp;</div><br>
> ><br>
> > <div>Any ideas? Thanks!</div><br>
<br> The most
> common issue we've seen people run into when installing from<br>
> source is that the default value for the `prefix` and some other<br>
> installation directories aren't what most expect.<br> <br> Still,
if
> you're running the daemon as root you shouldn't have any<br> issues
> w/r to permissions on the /dev/tpm0 device node so I wonder if<br>
> this node even exists on your platform. You may want to check to see
> if<br> `/dev/tpm0` is even present on your system. You're on an ARM
> platform<br> which means the kernel will only be aware of the TPM2
> device you've<br> added if you configure the device tree
properly.<br>
> <br> Regards,<br> Philip<br> <br> >
> <div>pi@raspberrypi:~/TPM/tpm2-abrmd $ uname
-a<br><br>
> > Linux raspberrypi 4.4.50-v7&#43; #1 SMP Wed Mar 14 14:01:00
> PDT 2018 armv7l GNU/Linux (&lt;== includes patch provided by
> Infineon)</div><br> ><br> >
> <div>&nbsp;</div><br>
> ><br>
> > <div>pi@raspberrypi:~/TPM/tpm2-abrmd $ dmesg | grep
> tpm<br><br> > [&nbsp;&nbsp;&nbsp;
3.700384]
> tpm_spi_tis spi0.1: 2.0 TPM (device-id 0xB6BC, rev-id
> 16)</div><br> ><br> >
> <div>&nbsp;</div><br>
> ><br>
> > <div>pi@raspberrypi:/etc $ cat
> /etc/os-release<br><br> >
PRETTY_NAME=&quot;Raspbian
> GNU/Linux 9 (stretch)&quot;<br><br> >
> NAME=&quot;Raspbian GNU/Linux&quot;<br><br>
>
> VERSION_ID=&quot;9&quot;<br><br>
> > VERSION=&quot;9 (stretch)&quot;<br><br>
>
> ID=raspbian<br><br> >
ID_LIKE=debian<br><br> >
> HOME_URL=&quot;<a href="http://www.raspbian.org/&quot"
>
target="_blank">http://www.raspbian.org/&quot</a&...
> > SUPPORT_URL=&quot;<a
> href="http://www.raspbian.org/RaspbianForums&quot"
>
target="_blank">http://www.raspbian.org/RaspbianForums&a...
> t;br><br> > BUG_REPORT_URL=&quot;<a
> href="http://www.raspbian.org/RaspbianBugs&quot"
>
target="_blank">http://www.raspbian.org/RaspbianBugs&...
> /div><br>
> > </div><br>
> > </div><br>
> >
</div></div></body></html><br>
> <br>
> > _______________________________________________<br>
> > tpm2 mailing list<br>
> > tpm2(a)lists.01.org<br>
> > <a href="https://lists.01.org/mailman/listinfo/tpm2"
>
target="_blank">https://lists.01.org/mailman/listinfo/tpm2&l...
> </div>
> </div>
> </div>
> </div>
>
> <div> </div>
>
> <div
class="signature"> </div></div></body></html>
_______________________________________________
tpm2 mailing list
tpm2(a)lists.01.org
https://lists.01.org/mailman/listinfo/tpm2
1:42 p.m.
-----Original Message-----
From: madprops(a)gmx.net [mailto:madprops@gmx.net]
Sent: Friday, March 23, 2018 1:12 PM
To: Roberts, William C <william.c.roberts(a)intel.com>
Cc: Tricca, Philip B <philip.b.tricca(a)intel.com>; tpm2(a)lists.01.org
Subject: Aw: RE: [tpm2] Problem with Infineon Iridium SLB 9670 TPM2.0
Thanks for the information, William and Philip! So yes, I installed the tools before
I installed the tabrmd. I found corresponsing messages in the config.log:
[...]
No package 'tcti-tabrmd' found
configure:12892: $? = 1
configure:12906: $PKG_CONFIG --exists --print-errors "tcti-tabrmd"
Package tcti-tabrmd was not found in the pkg-config search path.
Perhaps you should add the directory containing `tcti-tabrmd.pc'
to the PKG_CONFIG_PATH environment variable No package 'tcti-tabrmd' found
configure:12909: $? = 1
configure:12923: result: no
No package 'tcti-tabrmd' found
configure:12980: checking for CRYPTO
[...]
When I specify -v to the tool commands option list I get:
pi@raspberrypi:~/TPM/tpm2-tss $ sudo tpm2_getrandom 32 -v
tool="tpm2_getrandom" version="3.0.3"
tctis="socket,device,"
pi@raspberrypi:~/TPM/tpm2-tss $ sudo tpm2_getrandom 32 -T tabrmd
ERROR: Unknown tcti, got: "tabrmd"
I re-configured/built/installed the tools, but that did not help. I can still interact
with the TPM by stopping tabrmd and executing:
I'm assuming you checked to make sure configure picked up abrmd?
What does the -v for tools give you now?
Can you specify -T abrmd from the tools?
pi@raspberrypi:~/TPM/tpm2-tss $ sudo tpm2_getrandom 8 -T device:/dev/tpm0
0xBB 0x58 0x77 0x7F 0x58 0xFE 0x5D 0xFE
Gesendet: Freitag, 23. März 2018 um 20:58 Uhr
Von: "Roberts, William C" <william.c.roberts(a)intel.com>
An: "Tricca, Philip B" <philip.b.tricca(a)intel.com>,
"madprops(a)gmx.net"
<madprops(a)gmx.net>
Cc: "tpm2(a)lists.01.org" <tpm2(a)lists.01.org>
Betreff: RE: [tpm2] Problem with Infineon Iridium SLB 9670 TPM2.0
> -----Original Message-----
> From: tpm2 [mailto:tpm2-bounces@lists.01.org] On Behalf Of Philip
> Tricca
> Sent: Tuesday, March 20, 2018 12:20 PM
> To: madprops(a)gmx.net
> Cc: tpm2(a)lists.01.org
> Subject: Re: [tpm2] Problem with Infineon Iridium SLB 9670 TPM2.0
>
> Hey madprops,
>
> Thanks for the additional data.
>
> On Mon, Mar 19, 2018 at 09:17:33PM +0100, madprops(a)gmx.net wrote:
> > <html><head>
> > <meta http-equiv="Content-Type" content="text/html;
> > charset=utf-8"></head><body><div
style="font-family:
> > Verdana;font-size: 12.0px;"><div> <div>Thank you, Philip!
I
> > meanwhile noticed the tools work when I stop tpm2-abrmd and connect
> > directly to the TPM: </div>
>
> Well this debunks my theory that your issue was down in the dev tree
> :)
>
> > <div> </div>
> >
> > <div>pi@raspberrypi:~ $ sudo tpm2_pcrlist -T device:/dev/tpm0<br>
> > sha1 :<br>
> > 0 : 0000000000000000000000000000000000000000<br>
> > 1 : 0000000000000000000000000000000000000000<br>
> > [...]</div>
> >
> > <div> </div>
> >
> > <div>Please find below the information you asked for. While
> > tpm2-abrmd is running (as root) I still get this:</div>
> >
> > <div> </div>
> >
> > <div>pi@raspberrypi:~ $ tpm2_pcrlist<br>
> > ERROR: Failed to initialize tcti context: 0x1</div>
>
> Seeing this error while the tabrmd is running, but having the tools
> execute successfully with it stopped is a big hint. This indicates
> that the tools are probably trying to connect to the /dev/tpm0 device
> node directly instead of using the tabrmd.
>
> I've only see this happen if / when the tools are built in advance of
> building *and* installing the tabrmd. This happens because the tools
> build looks for the installed TCTI library for communicating with the
> daemon. If it doesn't find this library then the tools can't be linked
> against it and the build will fall back to using the device TCTI as
> the default. The `config.log` file in the tools build has the output from the
`configure` script and this will tell you which TCTI modules are enabled / disabled.
>
> Another way to check this theory is to take one of the tools
> executables and use `readelf` to dump information about the libraries
> that it links to. If the tabrmd TCTI library isn't listed then something it
up.
You can also specify -v to your tool commands option list to see what tcti's it
supports.
The first tcti in the string is the default IIC. I should have had an additional field
for
default.
On master, we switched to dynamic TCTIs with abrmd always being the default.
I think the 4.0 release, I'm going to add a field to explicitly say what the default
Is.
>
> Everything else below looks right.
>
> Regards,
> Philip
>
> > <div> </div>
> >
> > <div>pi@raspberrypi:~ $ export TPM2TOOLS_TCTI_NAME=tabrmd<br>
> > pi@raspberrypi:~ $ tpm2_pcrlist<br>
> > ERROR: Unknown tcti, got: "tabrmd"</div>
> >
> > <div> </div>
> >
> > <div>======== Versions:</div>
> >
> > <div>tpm2-abrmd: 1.3.1_rc0<br>
> > tpm2-tools: 3.0.3<br>
> > tpm2-tss: 1.4.0</div>
> >
> > <div> </div>
> >
> > <div>======== /dev/tpm0</div>
> >
> > <div>pi@raspberrypi:~ $ ls -la /dev/tpm0<br>
> > crw------- 1 root root 10, 224 Mar 17 21:35 /dev/tpm0</div>
> >
> > <div>======== tpm2-abrmd LOG</div>
> >
> > <div>root@raspberrypi:/home/pi# tpm2-abrmd<br>
> > ** INFO: tabrmd startup<br>
> > ** (process:1852): DEBUG: tcti_factory_set_property<br>
> > ** (process:1852): DEBUG: PROP_TCTI_TYPE<br>
> > ** (process:1852): DEBUG: value: 0x1<br>
> > ** (process:1852): DEBUG: tcti_factory_set_property<br>
> > ** (process:1852): DEBUG: TctiFactory set device_name: /dev/tpm0<br>
> > ** (process:1852): DEBUG: tcti_factory_set_property<br>
> > ** (process:1852): DEBUG: TctiFactory set socket_address:
> > 127.0.0.1<br>
> > ** (process:1852): DEBUG: tcti_factory_set_property<br>
> > ** (process:1852): DEBUG: TctiFactory set socket_port: 2321<br>
> > ** INFO: logging to stdout<br>
> > ** (tpm2-abrmd:1852): DEBUG: tcti_factory_get_tcti<br>
> > ** (tpm2-abrmd:1852): DEBUG: TctiDevice set filename: /dev/tpm0<br>
> > ** INFO: entering g_main_loop<br>
> > ** INFO: init_thread_func start<br>
> > ** (tpm2-abrmd:1852): DEBUG: random_class_init<br>
> > ** (tpm2-abrmd:1852): DEBUG: opening entropy source:
> > /dev/urandom<br>
> > ** (tpm2-abrmd:1852): DEBUG: reading from entropy source:
> > /dev/urandom<br>
> > ** (tpm2-abrmd:1852): DEBUG: seeding rand with -1263045295<br>
> > ** (tpm2-abrmd:1852): DEBUG: connection_manager_set_property:
> > 0x15c5ef0<br>
> > ** (tpm2-abrmd:1852): DEBUG: max_connections:
0x1b<br>
> > ** (tpm2-abrmd:1852): DEBUG: ConnectionManager: 0x15c5ef0<br>
> > ** (tpm2-abrmd:1852): DEBUG: IpcFrontendDbus set bus_name:
> > com.intel.tss2.Tabrmd<br>
> > ** (tpm2-abrmd:1852): DEBUG: ipc_frontend_connect: 0x75b01a08<br>
> > ** (tpm2-abrmd:1852): DEBUG: tcti_initialize: 0x15c5200<br>
> > ** (tpm2-abrmd:1852): DEBUG: sapi_context_init w/ Tcti:
> > 0x15c5200<br>
> > ** (tpm2-abrmd:1852): DEBUG: tcti_peek_context: 0x15c5200<br>
> > ** (tpm2-abrmd:1852): DEBUG: Allocating 0x1040 bytes for SAPI
> > context<br>
> > ** (tpm2-abrmd:1852): DEBUG: access_broker_set_property:
> > 0x75b0b720<br>
> > ** (tpm2-abrmd:1852): DEBUG: sapi_context:
> > 0x75b0a690<br>
> > ** (tpm2-abrmd:1852): DEBUG: access_broker_set_property:
> > 0x75b0b720<br>
> > ** (tpm2-abrmd:1852): DEBUG: tcti: 0x15c5200<br>
> > ** (tpm2-abrmd:1852): DEBUG: created AccessBroker: 0x75b0b720<br>
> > ** (tpm2-abrmd:1852): DEBUG: access_broker_init_tpm: 0x75b0b720<br>
> > ** INFO: on_bus_acquired: com.intel.tss2.Tabrmd<br>
> > ** INFO: on_name_acquired: com.intel.tss2.Tabrmd<br>
> > ** (tpm2-abrmd:1852): DEBUG: Got proxy object for DBus daemon.<br>
> > ** (tpm2-abrmd:1852): DEBUG:
> > access_broker_get_tpm_properties_fixed<br>
> > ** (tpm2-abrmd:1852): DEBUG: command_attrs_class_init<br>
> > ** (tpm2-abrmd:1852): DEBUG: created CommandAttrs: 0x75b01260<br>
> > ** (tpm2-abrmd:1852): DEBUG: GetCapabilty for 0x500 commands<br>
> > ** (tpm2-abrmd:1852): DEBUG: got attributes for 0x5a commands<br>
> > ** (tpm2-abrmd:1852): DEBUG: command_source_class_init<br>
> > ** (tpm2-abrmd:1852): DEBUG: command_source_set_properties:
> > 0x75b02c50<br>
> > ** (tpm2-abrmd:1852): DEBUG: command_attrs:
> 0x75b01260<br>
> > ** (tpm2-abrmd:1852): DEBUG: command_source_set_properties:
> > 0x75b02c50<br>
> > ** (tpm2-abrmd:1852): DEBUG: created command source: 0x75b02c50<br>
> > ** (tpm2-abrmd:1852): DEBUG: session_list_new with max-per-connection:
> > 0x4<br>
> > ** (tpm2-abrmd:1852): DEBUG: session_list_init<br>
> > ** (tpm2-abrmd:1852): DEBUG: session_list_set_property: 0x15c5fb0
> > max-per-connection: 4<br>
> > ** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property:
> > 0x75b02ca0<br>
> > ** (tpm2-abrmd:1852): DEBUG: in_queue:
0x75b00f90<br>
> > ** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property:
> > 0x75b02ca0<br>
> > ** (tpm2-abrmd:1852): DEBUG: access_broker:
> > 0x75b0b720<br>
> > ** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property:
> > 0x75b02ca0<br>
> > ** (tpm2-abrmd:1852): DEBUG: created ResourceManager: 0x75b02ca0<br>
> > ** (tpm2-abrmd:1852): DEBUG: response_sink_set_property<br>
> > ** (tpm2-abrmd:1852): DEBUG: setting
PROP_IN_QUEUE<br>
> > ** (tpm2-abrmd:1852): DEBUG: created response source: 0x75b012a8<br>
> > ** (tpm2-abrmd:1852): DEBUG: source_add_sink<br>
> > ** (tpm2-abrmd:1852): DEBUG: command_soruce_add_sink:
CommandSource:
> > 0x75b02c50 , Sink: 0x75b02ca0<br>
> > ** (tpm2-abrmd:1852): DEBUG: command_source_set_properties:
> > 0x75b02c50<br>
> > ** (tpm2-abrmd:1852): DEBUG: sink: 0x75b02ca0<br>
> > ** (tpm2-abrmd:1852): DEBUG: source_add_sink<br>
> > ** (tpm2-abrmd:1852): DEBUG: resource_manager_add_sink:
> > ResourceManager: 0x75b02ca0, Sink: 0x75b012a8<br>
> > ** (tpm2-abrmd:1852): DEBUG: resource_manager_set_property:
> > 0x75b02ca0<br>
> > ** (tpm2-abrmd:1852): DEBUG: sink: 0x75b012a8<br>
> > ** INFO: init_thread_func done<br>
> > ** (tpm2-abrmd:1852): DEBUG: resource_manager_thread start<br>
> > ** (tpm2-abrmd:1852): DEBUG: response_sink_thread blocking on input
> > queue: 0x75b00e50<br>
> > ** (tpm2-abrmd:1852): DEBUG: message_queue_dequeue 0x75b00e50<br>
> > ** (tpm2-abrmd:1852): DEBUG: message_queue_dequeue 0x75b00f90</div>
> >
> > <div> </div>
> >
> > <div>======== MISC</div>
> >
> > <div>pi@raspberrypi:~/TPM/tpm2-tss $ cat
> > /etc/dbus-1/system.d/tpm2-abrmd.conf<br>
> > <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus
> > Configuration 1.0//EN"<br>
> > "http://www.freedesktop.org/standards/dbus/1.0/busconfig.
> > dt
> > d"><br>
> > <busconfig><br>
> > <!-- ../system.conf have denied everything, so we just
> > punch some holes --><br> <policy
> > user="tss"><br>
<allow
> > own="com.intel.tss2.Tabrmd"/><br>
> > </policy><br>
> > <policy user="root"><br>
> > <allow
own="com.intel.tss2.Tabrmd"/><br>
> > </policy><br>
> > <policy
context="default"><br>
> > <allow
> > send_destination="com.intel.tss2.Tabrmd"/><br>
> > <allow
> > receive_sender="com.intel.tss2.Tabrmd"/><br>
> > </policy><br>
> > </busconfig></div>
> >
> > <div> </div>
> >
> > <div> </div>
> >
> > <div>
> > <div name="quote" style="margin:10px 5px 5px 10px; padding:
10px 0
> > 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word;
> > -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
> > <div style="margin:0 0 10px
0;"><b>Gesendet:</b> Montag, 19.
> > März
> > 2018 um 06:07 Uhr<br> <b>Von:</b> "Philip
Tricca"
> > &lt;philip.b.tricca(a)intel.com&gt;<br>
> > <b>An:</b> madprops@gmx.net<br>
> > <b>Cc:</b> tpm2@lists.01.org<br>
> > <b>Betreff:</b> Re: [tpm2] Problem with Infineon Iridium
SLB
> > 9670 TPM2.0</div>
> >
> > <div name="quoted-content">Hey there madprops,<br>
<br> On Sun, Mar
> > 18, 2018 at 02:04:15PM +0100, madprops(a)gmx.net wrote:<br>
>
> > <html><head><br> > <meta
> > http-equiv="Content-Type" content="text/html;
> >
charset=utf-8"></head><body><div
> > style="font-family: Verdana;font-size:
> > 12.0px;"><div><br> > <div
> > class="signature"><br>
> > > <div class="signature"><br>
> > > <div>I'm trying to get an &quot;Infineon
Iridium SLB
> > 9670 TPM 2.0 SPI Board&quot; run on my Raspberry Pi 3. I have
> > downloaded, compiled and installed the latest versions of
> > tpm2-abrmd, tpm2-tss and tpm2-tools. I started tpm2-abrmd as root,
> > hoping that I can then interact with the Infineon TPM using tpm2-tools.
> > &quot;tpm2_pcrlist&quot; and all other tpm2_* commands,
> > however, return error &quot;ERROR: Failed to initialize tcti
> > context: 0x1&quot;.</div><br> ><br>
<br> Can you please
> > provide some more info about your configuration?<br>
> > Specifically:<br>
> > - the version of the TSS2 libraries you're using<br>
> > - the version of the tabrmd you're using<br>
> > - the configuration options you're passing to each<br> <br> A
log
> > file from the tabrmd with logging dialed all the way up would be<br>
> > helpful. Since tabrmd uses glib and it's logging infrastructure you
> > dial<br> up the debug output all the way by setting
> > `G_MESSAGES_DEBUG=all` in the<br> daemon's environment.<br>
<br>
> > > <div>&nbsp;</div><br>
> > ><br>
> > > <div>Any ideas? Thanks!</div><br>
<br> The most
> > common issue we've seen people run into when installing from<br>
> > source is that the default value for the `prefix` and some other<br>
> > installation directories aren't what most expect.<br> <br>
Still, if
> > you're running the daemon as root you shouldn't have any<br>
issues
> > w/r to permissions on the /dev/tpm0 device node so I wonder if<br>
> > this node even exists on your platform. You may want to check to see
> > if<br> `/dev/tpm0` is even present on your system. You're on an ARM
> > platform<br> which means the kernel will only be aware of the TPM2
> > device you've<br> added if you configure the device tree
> > properly.<br> <br> Regards,<br> Philip<br> <br>
>
> > <div>pi@raspberrypi:~/TPM/tpm2-abrmd $ uname
-a<br><br>
> > > Linux raspberrypi 4.4.50-v7&#43; #1 SMP Wed Mar 14 14:01:00
> > PDT 2018 armv7l GNU/Linux (&lt;== includes patch provided by
> > Infineon)</div><br> ><br> >
> > <div>&nbsp;</div><br>
> > ><br>
> > > <div>pi@raspberrypi:~/TPM/tpm2-abrmd $ dmesg | grep
> > tpm<br><br> >
[&nbsp;&nbsp;&nbsp; 3.700384]
> > tpm_spi_tis spi0.1: 2.0 TPM (device-id 0xB6BC, rev-id
> > 16)</div><br> ><br> >
> > <div>&nbsp;</div><br>
> > ><br>
> > > <div>pi@raspberrypi:/etc $ cat
> > /etc/os-release<br><br> >
PRETTY_NAME=&quot;Raspbian
> > GNU/Linux 9 (stretch)&quot;<br><br> >
> > NAME=&quot;Raspbian GNU/Linux&quot;<br><br>
>
> > VERSION_ID=&quot;9&quot;<br><br>
> > > VERSION=&quot;9
(stretch)&quot;<br><br> >
> > ID=raspbian<br><br> >
ID_LIKE=debian<br><br> >
> > HOME_URL=&quot;<a
href="http://www.raspbian.org/&quot"
> >
target="_blank">http://www.raspbian.org/&quot</a&...
> > > SUPPORT_URL=&quot;<a
> > href="http://www.raspbian.org/RaspbianForums&quot"
> >
target="_blank">http://www.raspbian.org/RaspbianForums&a...;;
> > &l t;br><br> > BUG_REPORT_URL=&quot;<a
> > href="http://www.raspbian.org/RaspbianBugs&quot"
> >
target="_blank">http://www.raspbian.org/RaspbianBugs&...
> > t;
> > /div><br>
> > > </div><br>
> > > </div><br>
> > >
</div></div></body></html><br>
> > <br>
> > > _______________________________________________<br>
> > > tpm2 mailing list<br>
> > > tpm2(a)lists.01.org<br>
> > > <a href="https://lists.01.org/mailman/listinfo/tpm2"
> >
target="_blank">https://lists.01.org/mailman/listinfo/tpm2&l...
> > </div>
> > </div>
> > </div>
> > </div>
> >
> > <div> </div>
> >
> > <div
class="signature"> </div></div></body></html>
> _______________________________________________
> tpm2 mailing list
> tpm2(a)lists.01.org
> https://lists.01.org/mailman/listinfo/tpm2
8:51 a.m.
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.
Hence: https://github.com/flihp/meta-measured/pull/68
By the way, what's the difference between "abrmd" and "tabrmd"? It
seems
rather confusing that the tools list "tabrmd" as a TCTI, but in order to
use it one specifies "abrmd". Something feels wrong.
# tpm2_pcrlist -v
tool="tpm2_pcrlist" version=""
tctis="tabrmd,socket,device,"
# tpm2_pcrlist -T tabrmd
ERROR: Unknown tcti, got: "tabrmd"
# tpm2_pcrlist -T abrmd
sha1 :
0 : 0000000000000000000000000000000000000000
1 : 0000000000000000000000000000000000000000
...
10:40 a.m.
Hey Trevor,
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.
Hence: https://github.com/flihp/meta-measured/pull/68
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.
It seems
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.
Philip
# tpm2_pcrlist -v
tool="tpm2_pcrlist" version=""
tctis="tabrmd,socket,device,"
# tpm2_pcrlist -T tabrmd
ERROR: Unknown tcti, got: "tabrmd"
# tpm2_pcrlist -T abrmd
sha1 :
0 : 0000000000000000000000000000000000000000
1 : 0000000000000000000000000000000000000000
...
_______________________________________________
tpm2 mailing list
tpm2(a)lists.01.org
https://lists.01.org/mailman/listinfo/tpm2
1597
days inactive
1607
days old
10 comments
5 participants
participants (5)
-
Javier Martinez Canillas -
madprops＠gmx.net -
Philip Tricca -
Roberts, William C -
Trevor Woerner