-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce shim verifier client to the launcher #203
Conversation
The shim client will serve as a common abstraction between different attestation verifier implementations. For now, we just wrap the gRPC attestation verifier in the client. Eventually, with other attestation verifiers, we can support multiple protocols more easily as well as create a more robust fake.
There are already multiple files named attest.go, causing confusion. Since launcher/attest.go contains the attestation agent, agent.go is a better name.
Also fix minor lint nits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to also move all the other GRPC related stuff into launcher/internal/verifier
, so we can move it out of the way from the core application logic?
Export Challenge and VerifyAttestationResponse fields, except for Challenge.connID. Fix minor formatting issue. Remove logger from verifier.Client in favor of attestation verifier specific logging.
Sure, I moved it into internal/verifier and also regenerated the pbs/upgraded the protobuf lib |
The shim client will serve as a common abstraction between different attestation verifier implementations. For now, we just wrap the gRPC attestation verifier in the client. Eventually, with other attestation verifiers, we can support multiple protocols more easily as well as create a more robust fake.
This PR also renames
launcher/attest.go
tolauncher/agent.go