Skip to content

Revoked code signing certificate prevents installation on Win10 #21725

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

Closed
frennkie opened this issue Apr 18, 2021 · 7 comments
Closed

Revoked code signing certificate prevents installation on Win10 #21725

frennkie opened this issue Apr 18, 2021 · 7 comments

Comments

@frennkie
Copy link

I just downloaded Bitcoin Core for Windows 10 64bit but executing the installer fails with a UAC error message ("This app has been blocked for your protection"). The screen looks similar to this (can take a real screenshot in UAC):

error

I double checked and I have the correct file (according to the SHA256):

PS C:\Users\User\Downloads> Get-FileHash .\bitcoin-0.21.0-win64-setup.exe -Algorithm SHA256

Algorithm       Hash                                                                   Path
---------       ----                                                                   ----
SHA256          54050748EF4D4F000EA1ECE472491B3E5FD546EFC74ED52119354B2893F6624B      C:\Users\User\Downloads\bit...

I found out that the message from Windows appears when the is a problem with the code signing. I checked the certificate on the installer and really is listed as revoked - with the message: "This certificate was revoked by its certification authority."

revoked

@frennkie frennkie added the Bug label Apr 18, 2021
@jarolrod
Copy link
Member

This is being worked on, for now it is recommended to use the unsigned version: https://bitcoincore.org/bin/bitcoin-core-0.21.0/bitcoin-0.21.0-win64-setup-unsigned.exe

@brianddk
Copy link
Contributor

Please verify your downloads using GPG

@xavier2dc
Copy link

The signing certificate shows it was revoked on ‎Tuesday, ‎March ‎24, ‎2020. This seems back-dated. Normally, this happens when a publisher discovers a key compromise and wants to invalidate all binaries signed after the key was considered as compromised. Is it the case here?

I noticed the unsigned version was pushed on March 25, 2021, on the occasion of the signing certificate's expiration. That shouldn't be needed, as the installer was timestamped, therefore will remain valid despite the cert having expired. So, I don't see the connection between the expiration of the cert and its revocation effective a year earlier. Can someone clarify what's going on?

@achow101
Copy link
Member

See also: bitcoin-core/gui#252

The certificate was revoked when I went to renew it. I think it was revoked because I asked for a renewal while the certificate was still valid, but I'm not sure. All I know is that on March 16th, when I purchased a renewal for the certificate, the current one was immediately revoked with a backdated revocation. The key was not compromised and the revocation was not requested. The revocation reason is not known.

Due to changes to the code signing certificate OV requirements, we have been unable to get a new code signing certificate in order to remedy this issue. That is currently being worked on, and we should be able to get a certificate soon. Once the new certificate is issued, all of the affected versions will be re-signed and re-released.

@ricardofavero
Copy link

Any news about this problem? I think this is preventing many users from installing.

@sipa
Copy link
Member

sipa commented Apr 30, 2021

It's being worked on, but it needs a lot of administration to get a new certificate.

@achow101
Copy link
Member

achow101 commented Jun 3, 2021

We have a new certificate now so this can be closed.

@fanquake fanquake closed this as completed Jun 3, 2021
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Aug 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants