All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner at gmail.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] dlopen()'ing raw .so files considered bad
Date: Tue, 12 Jun 2018 07:43:08 -0400	[thread overview]
Message-ID: <20180612114308.GA1648@linux-uys3> (raw)
In-Reply-To: 9F48E1A823B03B4790B7E6E69430724D010EB3CC0F@EXCH2010B.sit.fraunhofer.de

[-- Attachment #1: Type: text/plain, Size: 820 bytes --]

Thank you everyone!! With the latest master, the .so handling is great:

	# tpm2_pcrlist -v
	tool="tpm2_pcrlist" version="3.0.2-537-ge25e9ee" tctis="dynamic" tcti-default=tabrmd dlclose=enabled

	# /etc/init.d/tpm2-abrmd start
	Starting TCG TSS2 Access Broker and Resource Management daemon: tpm2-abrmd.

	# tpm2_pcrlist 
	sha1:
	  0 : 0x0000000000000000000000000000000000000000
	  1 : 0x0000000000000000000000000000000000000000
	  2 : 0x0000000000000000000000000000000000000000
	[...]

	# /etc/init.d/tpm2-abrmd stop
	Stopping TCG TSS2 Access Broker and Resource Management daemon: tpm2-abrmd.

	# tpm2_pcrlist -T device:/dev/tpm0
	sha1:
	  0 : 0x0000000000000000000000000000000000000000
	  1 : 0x0000000000000000000000000000000000000000
	  2 : 0x0000000000000000000000000000000000000000
	[...]

             reply	other threads:[~2018-06-12 11:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 11:43 Trevor Woerner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-02  7:39 [tpm2] dlopen()'ing raw .so files considered bad Fuchs, Andreas
2018-06-02  2:19 Trevor Woerner
2018-06-01 16:51 Fuchs, Andreas
2018-06-01 16:49 Fuchs, Andreas
2018-06-01  0:15 Trevor Woerner
2018-05-31 23:18 Philip Tricca
2018-05-31 21:12 Roberts, William C
2018-05-31 20:46 Trevor Woerner

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=20180612114308.GA1648@linux-uys3 \
    --to=tpm2@lists.01.org \
    /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.