Browse Source
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
pull/145/head
Wladimir J. van der Laan
10 years ago
No known key found for this signature in database
GPG Key ID: 74810B012346C9A6
1 changed files with
5 additions and
9 deletions
-
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 |
|
|
|
|
