dogecoin

History

Graham Krizek fdf82ba181 Update all subprocess.check_output functions in CI scripts to be Python 3.4 compatible Removing the 'universal_newlines' and 'encoding' args from the subprocess.check_outputs fuction. 'universal_newlines' is supported in 3.4, but 'encoding' is not. Without specifying 'encoding' it will make a guess at encoding, which can break things on BSD systems. We must handle encoding/decoding ourselves until we can use Python 3.6		2019-01-18 09:36:39 -06:00
..
allow-incorrect-sha512-commits	Use python instead of slow shell script on verify-commits	2018-06-12 14:48:02 +00:00
allow-revsig-commits	Add Marco-expired-key-signed-commits to allow-revsig-commits	2018-03-28 14:55:50 -04:00
allow-unclean-merge-commits	Use python instead of slow shell script on verify-commits	2018-06-12 14:48:02 +00:00
gpg.sh	Merge #13454 : Make sure LC_ALL=C is set in all shell scripts	2018-06-18 13:18:12 +02:00
pre-push-hook.sh	Obsolete #!/bin/bash shebang	2018-06-20 11:12:41 +03:00
README.md	Improve documentation for running verify-commits.py script	2018-12-06 10:41:08 -05:00
trusted-git-root	Revert "test: Update trust git root".	2018-03-28 14:55:50 -04:00
trusted-keys	scripts: Add trusted key for Samuel Dobson	2018-12-04 13:51:53 +01:00
trusted-sha512-root-commit	Update trusted-sha512-root-commit for new bad tree hash	2017-03-09 09:53:19 -05:00
verify-commits.py	Update all subprocess.check_output functions in CI scripts to be Python 3.4 compatible	2019-01-18 09:36:39 -06:00

README.md

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 Python 3 script to verify commits against a trusted keys list.

Using verify-commits.py safely

Remember that you can't use an untrusted script to verify itself. This means that checking out code, then running verify-commits.py against HEAD is not safe, because the version of verify-commits.py 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.py 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.

Configuration files

trusted-git-root: This file should contain a single git commit hash which is the first unsigned git commit (hence it is the "root of trust").
trusted-sha512-root-commit: This file should contain a single git commit hash which is the first commit without a SHA512 root commitment.
trusted-keys: This file should contain a \n-delimited list of all PGP fingerprints of authorized commit signers (primary, not subkeys).
allow-revsig-commits: This file should contain a \n-delimited list of git commit hashes. See next section for more info.

Import trusted keys

In order to check the commit signatures you must add the trusted PGP keys to your machine. This can be done in Linux by running

gpg --recv-keys $(<contrib/verify-commits/trusted-keys)

Key expiry/revocation

When a key (or subkey) which has signed old commits expires or is revoked, verify-commits will start failing to verify all commits which were signed by said key. In order to avoid bumping the root-of-trust trusted-git-root file, individual commits which were signed by such a key can be added to the allow-revsig-commits file. That way, the PGP signatures are still verified but no new commits can be signed by any expired/revoked key. To easily build a list of commits which need to be added, verify-commits.py can be edited to test each commit with BITCOIN_VERIFY_COMMITS_ALLOW_REVSIG set to both 1 and 0, and those which need it set to 1 printed.