You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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.
The text was updated successfully, but these errors were encountered: