-
Notifications
You must be signed in to change notification settings - Fork 38.7k
windeploy: Renewed windows code signing certificate #25201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Concept ACK, thanks for updating the cert. |
|
This is the data inside the certificates file, dumped with: |
|
Metadata-only diff of our cert only, before and after this PR: --- a/01.txt 2022-05-26 15:47:38.796449649 +0200
+++ b/01.txt 2022-05-26 15:48:07.652166313 +0200
@@ -2,12 +2,12 @@
Data:
Version: 3 (0x2)
Serial Number:
- 05:23:7b:0a:6d:7a:67:45:13:f6:9e:e5:03:68:e2:28
+ 0a:65:6f:75:06:a5:ef:65:36:43:16:d4:4d:3d:d2:45
Signature Algorithm: sha256WithRSAEncryption
- Issuer: C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 Assured ID Code Signing CA
+ Issuer: C = US, O = "DigiCert, Inc.", CN = DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Validity
- Not Before: May 21 00:00:00 2021 GMT
- Not After : May 26 23:59:59 2022 GMT
+ Not Before: May 24 00:00:00 2022 GMT
+ Not After : May 29 23:59:59 2024 GMT
Subject: C = US, ST = Delaware, L = Lewes, O = Bitcoin Core Code Signing LLC, CN = Bitcoin Core Code Signing LLC
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
@@ -16,25 +16,24 @@
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Authority Key Identifier:
- 5A:C4:B9:7B:2A:0A:A3:A5:EA:71:03:C0:60:F9:2D:F6:65:75:0E:58
+ 68:37:E0:EB:B6:3B:F8:5F:11:86:FB:FE:61:7B:08:88:65:F4:4E:42
X509v3 Subject Key Identifier:
- 55:22:ED:66:78:9F:10:7B:DD:F3:3D:C4:EC:0C:8B:60:DB:83:89:A3
+ BC:2A:54:E7:C3:C8:BA:87:EF:D2:41:C9:DD:3C:B4:60:32:84:CB:77
X509v3 Key Usage: critical
Digital Signature
X509v3 Extended Key Usage:
Code Signing
X509v3 CRL Distribution Points:
Full Name:
- URI:http://crl3.digicert.com/sha2-assured-cs-g1.crl
+ URI:http://crl3.digicert.com/DigiCertTrustedG4CodeSigningRSA4096SHA3842021CA1.crl
Full Name:
- URI:http://crl4.digicert.com/sha2-assured-cs-g1.crl
+ URI:http://crl4.digicert.com/DigiCertTrustedG4CodeSigningRSA4096SHA3842021CA1.crl
X509v3 Certificate Policies:
- Policy: 2.16.840.1.114412.3.1
- CPS: http://www.digicert.com/CPS
Policy: 2.23.140.1.4.1
+ CPS: http://www.digicert.com/CPS
Authority Information Access:
OCSP - URI:http://ocsp.digicert.com
- CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2AssuredIDCodeSigningCA.crt
+ CA Issuers - URI:http://cacerts.digicert.com/DigiCertTrustedG4CodeSigningRSA4096SHA3842021CA1.crt
X509v3 Basic Constraints: critical
CA:FALSE
Signature Algorithm: sha256WithRSAEncryption |
|
ACK 7e9fe6d I have checked the changes made here in as far as I could and they look correct to me, and to form a correct certificate chain. |
|
I have signed the following message (uploaded as the file transfer.txt) with both the old and new keys: Signature with old key (uploaded as the file transfer.asc.txt): This can be verified using the following command on master (with the old code signing cert): Signature with new key (uploaded as the file newkey.asc.txt): This can be verified using the following command on this branch (with the new code signing cert): |
fanquake
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 7e9fe6d - tested above with OpenSSL 3 & faketime.
Github-Pull: bitcoin#25201 Rebased-From: 7e9fe6d
|
Backported to 23.x in #25316. |
Github-Pull: bitcoin#25201 Rebased-From: 7e9fe6d
|
Backported to 22.x in #25317. |
c4aacfb windeploy: Renewed windows code signing certificate (Andrew Chow) Pull request description: Backports: - #25201 ACKs for top commit: LarryRuane: utACK c4aacfb Tree-SHA512: cce6c85cecf0014e0b123b42e454db2123becf02f4274b1c355f69d8e7b8f77cd12af86adc251da8146b7bd3a55e9f47e3c1ed12f70c5267b3ac3283634526ec
4ebf6e3 p2p: always set nTime for self-advertisements (Martin Zumsande) 039ef21 tests: Use descriptor that requires both legacy and segwit (Andrew Chow) 5fd25eb tests: Calculate input weight more accurately (Andrew Chow) bd6d3ac windeploy: Renewed windows code signing certificate (Andrew Chow) 32fa522 test: ensure createmultisig and addmultisigaddress are not returning any warning for expected cases (brunoerg) 7658055 rpc: fix inappropriate warning for address type p2sh-segwit in createmultisig and addmultisigaddress (brunoerg) Pull request description: Backports: - #24454 - #25201 - #25220 - #25314 ACKs for top commit: LarryRuane: re-utACK 4ebf6e3 achow101: ACK 4ebf6e3 Tree-SHA512: add3999d0330b3442f3894fce38ad9b5adc75da7d681c949e1d052bac5520c2c6fb06eba98bfbeb4aa9a560170451d24bf00d08dddd4a3d080030ecb8ad61882
The current windows code signing certificate expires on May 26 23:59:59 2022 GMT. I have purchased a new code signing certificate which will expire on May 29 23:59:59 2024 GMT.