sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-26 12:32:48 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
f70157f5bb
dash/contrib/builder-keys/README.md
fanquake d529751f47
Merge bitcoin/bitcoin#24788: doc: Add gpg key import instructions for Windows 
107582039ac3cbfe072dc761f621c37c48aa2dc1 doc: Add gpg key import instructions for Windows (Dave Scotese)

Pull request description:

  This is a single commit to replace the three commits from #23916

  I propose this change so that Windows users can more easily import signers' keys.

ACKs for top commit:
  sipsorcery:
    tACK 107582039ac3cbfe072dc761f621c37c48aa2dc1.

Tree-SHA512: 7d4ec77ce10f751748c49f1453fa8baf0976b15af4f87dc27f4e2715ad73fbd7dc1f07fcf3e660d63a6b9eb895a5e4105774613d39a2328f73b92d9e6cff4ebd
2024-10-29 13:01:23 -05:00

988 B
Raw Blame History

PGP keys of builders and Developers

The file keys.txt contains fingerprints of the public keys of builders and active developers.

The keys are mainly used to sign git commits or the build results of builds.

The most recent version of each pgp key can be found on most pgp key servers.

Fetch the latest version from the key server to see if any key was revoked in the meantime. To fetch the latest version of all pgp keys in your gpg homedir,

gpg --refresh-keys

To fetch keys of builders and active developers, feed the list of fingerprints of the primary keys into gpg:

On *NIX:

while read fingerprint keyholder_name; do gpg --keyserver hkps://keys.openpgp.org --recv-keys ${fingerprint}; done < ./keys.txt

On Windows (requires Gpg4win >= 4.0.0):

FOR /F "tokens=1" %i IN (keys.txt) DO gpg --keyserver hkps://keys.openpgp.org --recv-keys %i

Add your key to the list if you provided Guix attestations for two major or minor releases of Dash Core.