From: Roberts, William C <william.c.roberts at intel.com>
To: tpm2@lists.01.org
Subject: [tpm2] Re: Can an unauthorized key be verified with activatecredential.
Date: Thu, 08 Sep 2022 16:00:13 +0000 [thread overview]
Message-ID: <69fb958270e1dbf667e194f4d596ff259c7debe5.camel@intel.com> (raw)
In-Reply-To: 20220907171416.6482.13937@ml01.vlan13.01.org
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
On Wed, 2022-09-07 at 17:14 +0000, Steven Clark wrote:
> I've been using a copy of tpm2_tools 4.0.x (and 5.x something) and I
> created a key just for parameter encryption that specifically has
> decrypt but adminwithpolicy and no userwithauth with the blank
> policy. The idea was that there was no way the key could be used to
> decrypt a session later as there's no valid way to authorize
> it. This seems to work just fine in Tools and the ESAPI so I figured
> nothing was wrong with it.
>
> I'm now trying to add verification via endorsement key to the
> process. I can run an activatecredential on essentially any key
> except this session key. Does the activatecredential command require
> authorization for all objects and that's why it's failing?
Yes, if you look at [1] table 12.5.2 it shows that the
@activateHandle and @keyHandle both need auth. So with no way to
authorize you cannot use it in the command. You could create a policy
that says the only way you can use the key is within the command of
ActicateCredential by using a Command Code Policy
see TPM2_PolicyCommandCode and the associated APIs and tpm2-tools
[1]
https://trustedcomputinggroup.org/wp-content/uploads/TCG_TPM2_r1p59_Part3_Commands_pub.pdf
>
> If so what's the recommended replacement? Can I just make a
> restricted encryption key and use that for establishing and
> encrypting/decrypting session?
> _______________________________________________
> tpm2 mailing list -- tpm2(a)lists.01.org
> To unsubscribe send an email to tpm2-leave(a)lists.01.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
reply other threads:[~2022-09-08 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69fb958270e1dbf667e194f4d596ff259c7debe5.camel@intel.com \
--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