From: Ted Kim <ted.h.kim at oracle.com>
To: tpm2@lists.01.org
Subject: [tpm2] get TPM applications to happily co-exist
Date: Tue, 27 Apr 2021 09:38:43 -0700 [thread overview]
Message-ID: <20aa5df0-e69a-46eb-975a-76b7ba7db298@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Folks,
The question has come up about how to get TPM applications to happily
coexist with minimal coordination.
One issue in the owner hierarchy is we want each application to to be
able to manage it's own objects but not affect those of the other
applications.
So for example, we only want application A to be able to evict
persistent handles owned by that application and not those of another
application B.
If I understand, tpm2_evictcontrol command, the authorization is on the
hierarchy and not on the object. Maybe I am thinking about this wrong,
but is there a way in the authorization to look at some property of the
object and tell who "owns" it and then figure out if this should be
allowed or not ?
Otherwise, I think, we end up building some other software which knows
how to authorize this on the hierarchy and keeps track of who owns what
and then issues the eviction only when the owner of an object is the
requester.
Am open to any suggestions.
Thanks,
-ted
reply other threads:[~2021-04-27 16:38 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=20aa5df0-e69a-46eb-975a-76b7ba7db298@oracle.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