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

Attestation for GARUDA #3

Open
p-j-l opened this issue Jun 7, 2021 · 1 comment
Open

Attestation for GARUDA #3

p-j-l opened this issue Jun 7, 2021 · 1 comment

Comments

@p-j-l
Copy link

p-j-l commented Jun 7, 2021

In the Objective section of GARUDA, there’s discussion of various ways to add trust to a server and it looks like there might be a technical way to add trust to one of the options. This is a quote:

It's open source! That is great, and whatever Garuda produces will be open source, but just because something is open source doesn't prove that the system running it is actually running that open source implementation as is — it's pretty easy to cheat.

Remote attestation is a feature of Trusted Execution Environments that can guarantee to a caller that a certain version of the software is running, we’ve explored it a bit here. It could work very nicely with Open Source software by giving browsers, or anyone, a way to guarantee that there’s no cheating by running other software so it might be worth including in the spec as a possibility.

@darobin
Copy link
Owner

darobin commented Jun 10, 2021

Yes, that's very much in line with the kind of thing I would like to see happen. If we can rely on technical means to eliminate overhead and weak points (eg. the need to have actual on-site audits) then the governance structure can be kept to a minimum.

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

No branches or pull requests

2 participants