Conversation
Collaborator
Author
|
flashbots/attested-tls-proxy#163 adds full vsocket support to attested-tls-proxy allowing us to test a full attested-tls workflow on nitro. More details coming soon |
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.
WIP
This adds experimental AWS Nitro support to attested-tls.
Pairs with flashbots/attested-tls-proxy#162 which adds vsocket support to
attestation-provider-serverallowing us to check that these nitro attestation documents will verify.There is also a flake for reproducibly building a docker container with
attestation-provider-server: https://github.com/flashbots/attested-tls-proxy/blob/peg/nitro-test/flake.nixHeres how to deploy using that flake (from the attested-tls-proxy repo on the paired branch):
This produces a Docker image tarball at result in the repo root.
The flake bakes in the enclave startup command, so the container starts the server in vsock mode and with
--server-attestation-type aws-nitroby default. That means you do not need to pass extra runtime flags when building the EIF.The server side then listens on vsock port 8000, and the parent host can connect with the client command using:
Which should verify the attestation-document, and dump it to a local file. But not actually check measurements.
This shows that nitro attestations can be verified but does not yet demonstrate an attested-tls workflow with nitro.