-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Sign windows installation package #277
Comments
Hi, @rainmaker2k! As you may know, Windows UAC bases its warning message on the reputation of the software and how many times has been downloaded and effectively used. To prevent this, developers can buy ad hoc certificates, to help with the process of being recognized as fast as possible as a valid application. Currently, we are renovating our certificate and changing our pipeline to avoid having the pfx certificate in our codebase. Unfortunately, our certifying company is still evaluating in these days the new certificate, so there is a small maintenance time window, in which in some cases UAC warns about the issue. It will be auto-resolved by itself in no more than 2-3 days. Sorry for the inconvenience |
Honestly speaking, there is a signature on both setup file and main exe, but cert is explicitly revoked — that's why Windows Defender was blocking it and doesn't allow to launch anyway. |
Hi @urz9999 unfortunately I think as per @3apa3a-b-ta3e 's comment, the certificate in use has been revoked, so now the latest release has been blocked from use even after installation: |
We know, we are currently asking Sectigo for support, it seems that the old certificate has been revoked while the new one is STILL in review. It's a very frustrating situation, but we hope to get in touch with them soon. Unfortunately, they already missed the SLA for replying to our support ticket. |
Leapp has become totally useless at this point |
We are working with the certificate supplier to fix this, and bear in mind that we want this issue fixed asap as much as you. To give you a bit of insight if we can’t come to an agreement with our supplier in a short time we’ll change supplier and request a new certificate. I can’t give you an ETA other than this is one of our top priorities right now. Leaving the certificate issue aside, the application logic fully works and you can compile and run it yourself if the windows certificate is blocking you. Also, Leapp is free and open-source and for this kind of problem there’s always the option of the enterprise support 🙂 I'll keep you guys updated as soon as we have news. |
We just released a patch for the Windows certificate. Please verify that it no longer shows the UAC warning. |
@urz9999 0.12.2 worked fine on Windows 11 |
Awesome. UAC warning is gone. I'll close this issue. |
Describe the bug
On Windows when you try to run the setup installation it will try to prevent the installation, because the package is not signed.
Leapp Version
0.12.0 (Windows)
To Reproduce
Steps to reproduce the behavior:
Microsoft Defender will block the installation and you can only continue if you explicitly.
Expected behavior
Installation should not be blocked by Defender or User Account Control
Desktop (please complete the following information):
Additional context
I'm on a company controlled laptop that doesn't allow any unsigned installations.
The text was updated successfully, but these errors were encountered: