diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-02-06 15:48:56 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-02-06 15:54:29 +0100 |
| commit | 88971352f6106d87156188cc0e29077baa05b86d (patch) | |
| tree | 57fb5b1531a2b8a88a0db611755967c6c4be59c2 /doc | |
| parent | c3451483d28381dd86ed89bfd62f99c6ba979986 (diff) | |
| parent | fabb72baa2fad62b6632dcb4be4f7a65135439cd (diff) | |
Merge #11909: contrib: Replace developer keys with list of pgp fingerprints
fabb72b contrib: Remove xpired 522739F6 key (MarcoFalke)
faeab66 contrib: Replace developer keys with list of pgp fingerprints (MarcoFalke)
Pull request description:
Having to host a copy of the keys in this repo was a common source of discussion and distraction, caused by problems such as:
* Outdated keys. Unclear whether and when to replace by fresh copies.
* Unclear when to add a key of a new developer or Gitian builder.
The problems are solved by
* Having no keys but only the fingerprints
* Adding a rule of thumb, when to add a new key
<strike>Moving the keys to a different repo solves none of these issues, but since the keys are not bound to releases or git branches of Bitcoin Core, they should live somewhere else.
Obviously, all keys are hosted and distributed on key servers, but were added to the repo solely for convenience and redundancy.
Moving the mirror of those keys to a different repo makes it less distracting to update them -- let's say -- prior to every major release.
I updated our `doc/release-process.md` to reflect the new location.
DEPENDS_ON https://github.com/bitcoin-core/gitian.sigs/pull/621
</strike>
Tree-SHA512: c00795a07603190e26dc4526f6ce11e492fb048dc7ef54b38f859b77dcde25f58ec4449f5cf3f85a5e9c2dd2743bde53f7ff03c8eccf0d75d51784a6b164e47d
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release-process.md | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/doc/release-process.md b/doc/release-process.md index 0f8dadfd1a..430a5a7ed3 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -137,10 +137,7 @@ Build output expected: ### Verify other gitian builders signatures to your own. (Optional) -Add other gitian builders keys to your gpg keyring, and/or refresh keys. - - gpg --import bitcoin/contrib/gitian-keys/*.pgp - gpg --refresh-keys +Add other gitian builders keys to your gpg keyring, and/or refresh keys: See `../bitcoin/contrib/gitian-keys/README.md`. Verify the signatures |