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

Ask an external notary for the hash of any tarball that we download from github releases #56

Open
Tracked by #53
alsuren opened this issue Jan 22, 2022 · 0 comments

Comments

@alsuren
Copy link
Collaborator

alsuren commented Jan 22, 2022

After talking to my housemate about threat models, I don't think that storing signatures on a server that I control really closes any attack vectors. It might be interesting to ask an external notary to tell us the hash of the tarball from github-releases when we download it. We could then know whether it has ever changed.

The phrase that google uses for this is "binary transparency" - they write things to an append-only log. See https://transparency.dev/ and https://www.sigstore.dev/ for details.

@alsuren alsuren changed the title Check signatures and unpack. Ask an external notary for the hash of any tarball that we download from github releases Jan 22, 2022
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

1 participant