sipsorcery gitian key #16581

pull sipsorcery wants to merge 1 commits into bitcoin:master from sipsorcery:add_gitian_key changing 1 files +1 −0

sipsorcery commented at 4:04 PM on August 10, 2019: member

No description provided.
sipsorcery gitian key. 9063911017

in contrib/gitian-keys/keys.txt:33 in f2d68b34a7 outdated

  29 | @@ -30,3 +30,4 @@ ED9BDF7AD6A55E232E84524257FF9BDBCC301009 Sjors Provoost
  30 |  AEC1884398647C47413C1C3FB1179EB7347DC10D Warren Togami
  31 |  79D00BAC68B56D422F945A8F8E3A8F3247DBCBBF Willy Ko
  32 |  71A3B16735405025D447E8F274810B012346C9A6 Wladimir J. van der Laan
  33 | +9D3CC86A72F8494342EA5FD10A41BDC3F4FAFF1C Aaron Clauson (sipsorcery)

hebasto commented at 4:31 PM on August 10, 2019:

It should be in the first name alphabetic order.

sipsorcery commented at 4:39 PM on August 10, 2019:

Ahh somehow didn't spot that. Fixed now. Woo hoo straight to the top of the list (if accepted that is)!

sipsorcery force-pushed on Aug 10, 2019
DrahtBot added the label Build system on Aug 10, 2019
DrahtBot added the label Scripts and tools on Aug 10, 2019
MarcoFalke removed the label Build system on Aug 11, 2019
fanquake added the label Docs on Aug 12, 2019

fanquake commented at 12:58 AM on August 12, 2019: member

Concept ACK 906391101754f0d5188b561ff820fa4e7784d634

gpg --recv-key 9D3CC86A72F8494342EA5FD10A41BDC3F4FAFF1C
gpg: key 0A41BDC3F4FAFF1C: no user ID
gpg: Total number processed: 1

gitian.sigs $ gpg --verify 0.18.1-linux/sipsorcery/bitcoin-linux-0.18-build.assert.sig 0.18.1-linux/sipsorcery/bitcoin-linux-0.18-build.assert
gpg: Signature made Sat 10 Aug 09:45:44 2019 AWST
gpg:                using RSA key 9D3CC86A72F8494342EA5FD10A41BDC3F4FAFF1C
gpg: key 0A41BDC3F4FAFF1C: no user ID
gpg: Total number processed: 1
gpg: Can't check signature: No public key

Has been producing sigs for most of the year and has now signed for 3 major releases. @sipsorcery Is there any particular reason you haven't been building and commiting the Windows signed sigs?

I'd also have no issue with adding sipsorcery to the bitcoin/bitcoin org, as he and NicolasDorier are basically taking care of anything Windows related.

sipsorcery commented at 7:31 AM on August 12, 2019: member

@fanquake I had assumed the Windows signed sigs needed the private code signing key. I guess that's not the case? I'll take a look at the docs again.
laanwj commented at 11:03 AM on August 12, 2019: member

ACK 906391101754f0d5188b561ff820fa4e7784d634
laanwj merged this on Aug 12, 2019
laanwj closed this on Aug 12, 2019
laanwj referenced this in commit 00dad5e0e1 on Aug 12, 2019
laanwj commented at 1:13 PM on August 12, 2019: member

@fanquake I had assumed the Windows signed sigs needed the private code signing key. I guess that's not the case? I'll take a look at the docs again.

No, that's not the case, the signing stage is really "attach existing signature to known output" not so much "sign"
DrahtBot locked this on Dec 16, 2021

Contributors

Labels

Docs Scripts and tools