Repository navigation
Conversation
Co-authored-by: Codex <[email protected]>
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.
what changed
(runId, runSecret)with verifier-service over mTLS (POST /runs) before launching, and passes the secret in user data. The host serves it to the enclave on vsock 5001.SHA-256(runSecret)inRunBindingTable(1 h TTL)./challengerejects arunIdwhose secret is not registered, and the issued challenge row carries the hash./challengeand setsuser_data = SHA-256(secret)in the NSM attestation./attestrejects a document whoseuser_datadoes not match the challenge row.make -C secure/sce gen-client-cert), added to the verifier truststore.VERIFIER_RUNS_URLand the@srads/common/tlspin helper wire it up.docs/e2e-secure-rads.txt,docs/getting-started.md,docs/cost-service.md.why
Refs #120. The host chooses the
runIdthe enclave runs under, so a compromised host can attribute a genuine, correctly measured enclave's PDM fetch, KMS decrypt, DSAR entry and cost to another run. The registered secret makes therunIda capability: only that run's host receives it, and the verifier refuses a challenge for any other id.PCRs cannot fix this. One EIF per algorithm means PCR0/1/2 are identical for every run, so the binding lives in the attestation
user_dataand the challenge row, not in a measurement.verification
gofmt -l . && go build ./... && go vet ./... && go test ./...insecure/sce-unit(no test files).tsc --noEmitandbiome check srcinsecure/verifier-serviceandsecure/sce/execution-service.serverless.ymlfiles parsed as YAML.notes
Draft. This binds the enclave's attested work to its run. The
GET /run/{runId}result body still needs #93's signed result to be trustworthy.Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.