選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
PenTesting 5da1adce92
Regex hardening to fix CVE-2018-12356.
2年前
..
README.md Add README for verify-commits 4年前
allow-revsig-commits Allow to whitelist commits signed with a revoked key 4年前
gpg.sh Regex hardening to fix CVE-2018-12356. 2年前
pre-push-hook.sh [copyright] add MIT license headers to .sh scripts where missing 4年前
trusted-git-root Adjust verify-commits to gitian-builder 4年前
trusted-keys Adjust verify-commits to gitian-builder 4年前
verify-commits.sh [copyright] add MIT license headers to .sh scripts where missing 4年前

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 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.