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

Having a better error message for missing gpg key during package build #187

Open
2 tasks
kushaldas opened this issue Aug 19, 2020 · 0 comments
Open
2 tasks

Comments

@kushaldas
Copy link
Contributor

We now have support for reproducible tarball dynamically via #185. But, if the GPG key is missing on the system, it will provide
an error message saying not signed with KEYID.

Receiving objects: 100% (9312/9312), 6.98 MiB | 4.09 MiB/s, done.
Resolving deltas: 100% (6892/6892), done.
Failed to verify 0.2.1, not signed with 22245C81E3BAEB4138B36061310F561200F4AD77
make: *** [Makefile:9: securedrop-client] Error 2

But, the actual error is missing key, if we see not signed, that may mean an attack of some sort :)

How to reproduce?

  • Delete the key gpg2 --delete-keys 22245C81E3BAEB4138B36061310F561200F4AD77
  • Try to build securedrop-client make securedrop-client
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