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

Eliminate gpg usage inside the VM and just do the signing outside #151

Open
daira opened this issue Mar 13, 2023 · 0 comments
Open

Eliminate gpg usage inside the VM and just do the signing outside #151

daira opened this issue Mar 13, 2023 · 0 comments

Comments

@daira
Copy link
Contributor

daira commented Mar 13, 2023

Using gpg inside the VM is far more hassle that it's worth. It also appears that the key import and signing inside the VM requires a private key without a passphrase, which introduces an unnecessary security weakness (I nearly compromised my key trying to debug it), and I don't know how to do it without falling back to gnupg 1.4.

The gitian signatures do not need to be deterministic; only the information being signed is expected to be deterministic.

Signing outside the VM could still be automated. However, philosophically I also dislike that we are even attempting to automate it. The signer should have explicit control of what is signed, and that's easier if they just do it manually.

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