From: scott.r.eisele at gmail.com
To: tpm2@lists.01.org
Subject: [tpm2] Re: TPM for SSH authentication
Date: Wed, 04 Aug 2021 20:21:03 +0000 [thread overview]
Message-ID: <20210804202103.2797.21889@ml01.vlan13.01.org> (raw)
In-Reply-To: SN6PR11MB3437F8CC917EF93CFA4765ECB8E39@SN6PR11MB3437.namprd11.prod.outlook.com
[-- Attachment #1: Type: text/plain, Size: 224 bytes --]
Thanks for pointing me to that resource. It turned out that the command I thought was failing was still storing the key. The message about the error with Fapi_List() is still present but doesn't seem to impact this use case.
next reply other threads:[~2021-08-04 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 20:21 scott.r.eisele [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-21 17:03 [tpm2] Re: TPM for SSH authentication Roberts, William C
2021-07-20 7:11 Anthony Arrascue
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=20210804202103.2797.21889@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