{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigbcltrfkzsn5xbegyuzh5pirpifozkdy4pnwn4u5qorki7eguggq",
    "uri": "at://did:plc:uxkrhzvf6obbsoh5nf2gkpj5/app.bsky.feed.post/3ml4hddpqxpq2"
  },
  "path": "/tpm-2-0-sealing-policies-with-wolftpm-pcr-policies-policy-authorize-and-nv-storage-for-tpm-2-0-secrets/?utm_source=rss&utm_medium=rss&utm_campaign=tpm-2-0-sealing-policies-with-wolftpm-pcr-policies-policy-authorize-and-nv-storage-for-tpm-2-0-secrets",
  "publishedAt": "2026-05-05T12:00:06.000Z",
  "site": "https://www.wolfssl.com",
  "tags": [
    "wolfTPM",
    "Uncategorized"
  ],
  "textContent": "Background: TPM 2.0 Sealing and PCR Policies TPM 2.0 sealing binds a secret to a set of Platform Configuration Register (PCR) values. The TPM will only release the secret when the current PCR state matches what was recorded at seal time. This is the foundation for measured boot, disk encryption key protection, and platform attestation. […]",
  "title": "TPM 2.0 Sealing Policies with wolfTPM: PCR Policies, Policy Authorize, and NV Storage for TPM 2.0 Secrets"
}