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

RFC: Run Trustee inside of an enclave #542

Open
fitzthum opened this issue Oct 21, 2024 · 0 comments
Open

RFC: Run Trustee inside of an enclave #542

fitzthum opened this issue Oct 21, 2024 · 0 comments

Comments

@fitzthum
Copy link
Member

Since Trustee needs to run in a trusted environment, it could make sense to run it inside of an enclave. This is easier said and done.

Here is a sketch of how we could run Trustee inside of not just any enclave, but CoCo.

One one level, it should be easy to run Trustee in CoCo. We can already deployee Trustee in k8s. If we add some runtime classes, it will work for CoCo. On top of that, we probably want to use sealed secrets to provide certain parts of the configuration, such as the token signing keys.

The big question is how we attest this environment. It might seem like we have a tautological situation here, but actually I think it's reasonable to have a basic attestation tool that can attest Trustee only.

So the question is really how we create a simple, static attestation tool (likely part of trustee-cli) that will listen for a resource request, carry out the KBS protocol, and provide secrets. Hopefully we can reuse logic from Trustee, but the implementation is still a little fuzzy to me.

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

No branches or pull requests

1 participant