aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2014-09-27 15:58:47 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2014-09-27 15:58:55 +0200
commita38eaea082692d0dac6996dcace2084cd7f29179 (patch)
treef1ade0c7c9c4c35711d899b8891f3b9259c7780c
parent2c45f49cde5c033daa17340c32a960e32f737a08 (diff)
doc: Update SHA256SUMS.asc step in release-process.md
- The Hash: header is prepended by gpg, and states the hashing used by gpg, not what is used to hash the files - Add more detailed steps
-rw-r--r--doc/release-process.md14
1 files changed, 5 insertions, 9 deletions
diff --git a/doc/release-process.md b/doc/release-process.md
index 8934be66c4..5b8029955d 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -178,15 +178,11 @@ Commit your signature to gitian.sigs:
Note: only Gavin has the code-signing keys currently.
-- Create `SHA256SUMS.asc` for builds, and PGP-sign it. This is done manually.
- Include all the files to be uploaded. The file has `sha256sum` format with a
- simple header at the top:
-
-```
-Hash: SHA256
-
-0060f7d38b98113ab912d4c184000291d7f026eaf77ca5830deec15059678f54 bitcoin-x.y.z-linux.tar.gz
-...
+- Create `SHA256SUMS.asc` for the builds, and GPG-sign it:
+```bash
+sha256sum * > SHA256SUMS
+gpg --clearsign SHA256SUMS # outputs SHA256SUMS.asc
+rm SHA256SUMS
```
- Upload zips and installers, as well as `SHA256SUMS.asc` from last step, to the bitcoin.org server