Skip to content
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

Spike: run signed oracle binary #563

Closed
Tracked by #82
mudler opened this issue Sep 24, 2024 · 3 comments
Closed
Tracked by #82

Spike: run signed oracle binary #563

mudler opened this issue Sep 24, 2024 · 3 comments

Comments

@mudler
Copy link
Contributor

mudler commented Sep 24, 2024

High level with TEE

  • Create a reproducible build
  • Add code to generate an attestation document at runtime for your chosen trusted execution environment (e.g. AMD SEV, Intel SGX, or AWS Nitro Enclaves)
  • Build the application enclave and measure it.
  • Run the enclave.

Now that we have known-good measurements, clients can attempt verification:

  • The client fetches the enclave’s attestation document using a challenge-response mechanism.
  • The client verifies the attestation document, comparing the software measurement of the running software with the known-good measurement obtained from the build. If they match, trust in the software is established.

Notes / Open questions

  • Increased rewards for those that run signed binary (might be required to run in a VM >?)

References

@mudler
Copy link
Contributor Author

mudler commented Sep 25, 2024

very interesting paper on the subject: https://arxiv.org/pdf/2402.08908

@mudler
Copy link
Contributor Author

mudler commented Sep 25, 2024

High level with TEE

  • Create a reproducible build
  • Add code to generate an attestation document at runtime for your chosen trusted execution environment (e.g. AMD SEV, Intel SGX, or AWS Nitro Enclaves)
  • Build the application enclave and measure it.
  • Run the enclave.

Now that we have known-good measurements, clients can attempt verification:

  • The client fetches the enclave’s attestation document using a challenge-response mechanism.
  • The client verifies the attestation document, comparing the software measurement of the running software with the known-good measurement obtained from the build. If they match, trust in the software is established.

@mudler
Copy link
Contributor Author

mudler commented Oct 15, 2024

draft PR in : #588

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant