Repository navigation
Conversation
ameba23
force-pushed
the
peg/attestation-provider-uses-unix-socket
branch
from
October 28, 2026 15:26
70471ea to
3433691
Compare
ameba23
force-pushed
the
peg/attestation-provider-uses-unix-socket
branch
from
October 29, 2026 08:19
4ed3c46 to
5dfc570
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This improves security of the attestation provider server by using unix sockets rather than the loopback interface, giving stronger guarantees that it runs on the same host as the caller.
It also switches the protocol used from HTTP to a very simple binary protocol.
The client who wants an attestation sends the 64 byte quote input, and the service responds with a SCALE encoded
Result<AttestationExchangeMessage, ProviderError>.