To: tpm2@lists.01.org
Subject: [tpm2] Re: Stablishing trust on to TPM simulator
Date: Sat, 23 May 2020 19:49:47 +0000 [thread overview]
Message-ID: <20200523194947.2859.89837@ml01.vlan13.01.org> (raw)
In-Reply-To: 20200520184131.2843.35549@ml01.vlan13.01.org
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hi Desai and Roberts.
Thank you for yours responses.
Yes, Desai, I already knew the Keylime project. And, indeed, I got the feeling that they were doing what I wanted. But in a first moment, I want to do the demo by myself, so I can better understand the concepts and steps involved to create the chain of trust. Perhaps I'll consider using Keylime when I'll be comfortable with the whole process.
Roberts, the path you pointed was really correct. Thank you.
I created an issue on the swtpm project and Stefan extended a wiki about certificate creation.
For those interested, it is here: https://github.com/stefanberger/swtpm/wiki/Certificiates-created-by-swtpm_setup#verifying-your-ek-cert-against-the-ca
Regards
next reply other threads:[~2020-05-23 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 19:49 [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-20 18:41 [tpm2] Re: Stablishing trust on to TPM simulator william.c.roberts
2020-05-20 18:24 Imran Desai
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=20200523194947.2859.89837@ml01.vlan13.01.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox