Service Discovery #2

Open
opened 2025-09-09 02:16:02 +00:00 by ryan · 3 comments
Owner

I think we should have a socket pattern like /run/<service>/bootproof.sock for services to be able to listen for bootproof and provide metadata that can be used for other services. This could be useful for Keyfork reconstitution ephemeral-key signing keys or TLS certificate fingerprints.

I think we should have a socket pattern like `/run/<service>/bootproof.sock` for services to be able to listen for bootproof and provide metadata that can be used for other services. This could be useful for Keyfork reconstitution ephemeral-key signing keys or TLS certificate fingerprints.
Author
Owner

bootproofd doesn't need to care what the actual data is, just that it's <=512 bytes, and included in the attestation doc.

bootproofd doesn't need to care what the actual data is, just that it's <=512 bytes, and included in the attestation doc.
Author
Owner

ReprOS could include SSH known_hosts keys.

ReprOS could include SSH known_hosts keys.
Author
Owner

Service workers could get an attested hash of a new version of the service worker.

Service workers could get an attested hash of a new version of the service worker.
ryan added this to the Verifiable Compute Platform project 2025-09-21 01:29:32 +00:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/bootproof#2
No description provided.