From: Felix Rubio Dalmau <felix at kngnt.org>
To: tpm2@lists.01.org
Subject: [tpm2] Re: System design question
Date: Sun, 21 Aug 2022 14:05:57 +0200 [thread overview]
Message-ID: <4206872.ejJDZkT8p0@polaris> (raw)
In-Reply-To: 22755930.6Emhk5qWAg@polaris
[-- Attachment #1: Type: text/plain, Size: 149 bytes --]
My apologies, I have not played with TPM for long time: I had forgotten I
could tpm2_nvdefine, and then tpm2_nvwrite/nvread.
Regards!
Felix
next reply other threads:[~2022-08-21 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 12:05 Felix Rubio Dalmau [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-22 13:08 [tpm2] Re: System design question Roberts, William C
2022-08-22 13:09 Roberts, William C
2022-08-22 16:02 Roberts, William C
2022-08-28 9:38 Felix Rubio Dalmau
2022-08-31 19:21 Roberts, William C
2022-08-31 21:21 David Challener
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=4206872.ejJDZkT8p0@polaris \
--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