From: Tommaso Corda <tommasocorda at hotmail.it>
To: tpm2@lists.01.org
Subject: [tpm2] R: Wildcard policies for NVindexes
Date: Fri, 24 May 2019 08:07:56 +0000 [thread overview]
Message-ID: <AM6PR10MB2134B29444A9E702DE553757AE020@AM6PR10MB2134.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: 9F48E1A823B03B4790B7E6E69430724D0163A458F6@exch2010c.sit.fraunhofer.de
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
https://ebrary.net/24814/computer_science/flexible_wild_card_policy
Flexible (Wild Card) Policy - A Practical Guide to TPM 2.0<https://ebrary.net/24814/computer_science/flexible_wild_card_policy>
One major problem with the TPM 1.2 design was the brittleness of PCRs. When an entity was locked to a PCR, it was not possible to change the required values of the PCR after it was so locked.
ebrary.net
________________________________
Da: Fuchs, Andreas <andreas.fuchs(a)sit.fraunhofer.de>
Inviato: venerdì 24 maggio 2019 10:05
A: Tommaso Corda; tpm2(a)lists.01.org
Oggetto: RE: Wildcard policies for NVindexes
Could you explain to me, what a Wildcard policy supposingly is ?
I've never heard of this.
________________________________
From: tpm2 [tpm2-bounces(a)lists.01.org] on behalf of Tommaso Corda [tommasocorda(a)hotmail.it]
Sent: Friday, May 24, 2019 10:03
To: tpm2(a)lists.01.org
Subject: [tpm2] Wildcard policies for NVindexes
Hello everyone.
Can anybody explain me how to use wildcard policies to create a NVindex and how to use a wildcard policy to access that NVindex?
Thanks.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4402 bytes --]
reply other threads:[~2019-05-24 8:07 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=AM6PR10MB2134B29444A9E702DE553757AE020@AM6PR10MB2134.EURPRD10.PROD.OUTLOOK.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.