dogecoin/contrib/verify-commits
Ross Nicoll f00d2ca3fb Remove Bitcoin values from commit verifier (#1458)
Unused currently, but changed to Dogecoin specific stuff incase of future implementation.
2019-03-25 05:36:12 +00:00
..
allow-revsig-commits Add Pieter's old signed commits to revsig-commits 2017-02-28 16:45:01 +01:00
gpg.sh Fix regsig checking for subkey sigs in verify-commits 2017-03-05 19:09:49 +01:00
pre-push-hook.sh Remove Bitcoin values from commit verifier (#1458) 2019-03-25 05:36:12 +00:00
README.md Add README for verify-commits 2016-06-09 13:58:29 -04:00
trusted-git-root Remove Bitcoin values from commit verifier (#1458) 2019-03-25 05:36:12 +00:00
trusted-keys Remove Bitcoin values from commit verifier (#1458) 2019-03-25 05:36:12 +00:00
verify-commits.sh Require merge commits merge branches on top of other merge commits 2017-02-01 18:22:27 -05:00

Tooling for verification of PGP signed commits

This is an incomplete work in progress, but currently includes a pre-push hook script (pre-push-hook.sh) for maintainers to ensure that their own commits are PGP signed (nearly always merge commits), as well as a script to verify commits against a trusted keys list.

Using verify-commits.sh safely

Remember that you can't use an untrusted script to verify itself. This means that checking out code, then running verify-commits.sh against HEAD is not safe, because the version of verify-commits.sh that you just ran could be backdoored. Instead, you need to use a trusted version of verify-commits prior to checkout to make sure you're checking out only code signed by trusted keys:

git fetch origin && \
  ./contrib/verify-commits/verify-commits.sh origin/master && \
  git checkout origin/master

Note that the above isn't a good UI/UX yet, and needs significant improvements to make it more convenient and reduce the chance of errors; pull-reqs improving this process would be much appreciated.