feat: workload attestation

[maceip]

updates ->

• Oak: workload attestation binding:
  • the client now configures only the workload verifier.
• README.md:
  • the privateinference package provides:
    • network isolation from PCC through PCS,
    • encrypted Oak session,
    • anonymous authorization token,
    • optional device attestation,
    • possible server confidential compute, depending on unseen server-side code.
  • which plants it firmly in the "Confidential X" category, not in the "Private X" category. I made this distinction clear

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[abo332ode-beep]

updates ->

• Oak: workload attestation binding:
  • the client now configures only the workload verifier.
• README.md:
  • the privateinference package provides:
    • network isolation from PCC through PCS,
    • encrypted Oak session,
    • anonymous authorization token,
    • optional device attestation,
    • possible server confidential compute, depending on unseen server-side code.
  • which plants it firmly in the "Confidential X" category, not in the "Private X" category. I made this distinction clear

• [ ]

[abo332ode-beep]

updates ->

• Oak: workload attestation binding:
  • the client now configures only the workload verifier.
• README.md:
  • the privateinference package provides:
    • network isolation from PCC through PCS,
    • encrypted Oak session,
    • anonymous authorization token,
    • optional device attestation,
    • possible server confidential compute, depending on unseen server-side code.
  • which plants it firmly in the "Confidential X" category, not in the "Private X" category. I made this distinction clear

• [ ]

[zaragozay2000-ux]

I like it in general please allow me to say great job guys

[zaragozay2000-ux]

Great

[abbarquin13-cyber]

FUCK YOU!!!

…

On Fri, May 8, 2026, 7:39 PM abo332ode-beep ***@***.***> wrote: *abo332ode-beep* left a comment (google/private-compute-services#95) <#95 (comment)> updates -> - *Oak*: workload attestation binding: - the client now configures only the workload verifier. - *README.md*: - the privateinference package provides: - network isolation from PCC through PCS, - encrypted Oak session, - anonymous authorization token, - optional device attestation, - possible server confidential compute, depending on unseen server-side code. - which plants it firmly in the "Confidential X <https://docs.cloud.google.com/confidential-computing/confidential-vm/docs/confidential-vm-overview>" category, not in the "Private X" category. I made this distinction clear - [ ] — Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B4OKBHYTHZWOMNFXCK3COLD4ZXBQRAVCNFSM6AAAAACYQY7DZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMBWGEYTENJQGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>