Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Windows Defender shows aggressive warning #71

Open
holmesworcester opened this issue Aug 3, 2021 · 1 comment
Open

Windows Defender shows aggressive warning #71

holmesworcester opened this issue Aug 3, 2021 · 1 comment
Labels
bug Something isn't working
Projects
Quiet

Comments

@holmesworcester
Copy link
Contributor

holmesworcester commented Aug 3, 2021 •
edited

Options for fixing:

  1. Make an installer that we sign by hand and update rarely that downloads the latest version.
  2. Automate the EV signing process using a HSM and some bureaucratic process. See: Support for HSM stored certificates? vcsjones/AzureSignTool#112

The latter is better so we should try that first
@vinkabuki vinkabuki transferred this issue from TryQuiet/ZbayLite Jan 4, 2022
EmiM pushed a commit that referenced this issue Feb 16, 2022
@Farfurix @EmiM
Add the publish-please config file (#71)
093d11c
@holmesworcester holmesworcester changed the title Fix Windows Defender warning by using EV cert to hand sign a rarely-updated installer Windows Defender shows aggressive warning May 10, 2022
@holmesworcester holmesworcester added the bug Something isn't working label May 10, 2022
@holmesworcester holmesworcester moved this from Backlog to Sprint in Quiet May 10, 2022
@holmesworcester
Copy link
Contributor Author

holmesworcester commented May 10, 2022 •
edited

bumped up the priority on this because we have to renew the cert now, and if we can't get this working with digicert we could find another provider.

More instructions here: https://www.codiga.io/blog/notarize-sign-electron-app/

@holmesworcester holmesworcester moved this from Sprint to Backlog - Desktop & Backend in Quiet Jun 4, 2022
@holmesworcester holmesworcester moved this from Backlog - Desktop & Backend to Blocked in Quiet Jun 15, 2022
@holmesworcester holmesworcester moved this from Blocked to Sprint in Quiet Jun 15, 2022
@holmesworcester holmesworcester moved this from Sprint to Next Sprint in Quiet Jun 15, 2022
@holmesworcester holmesworcester moved this from Next Sprint to Backlog - Desktop & Backend in Quiet Jun 15, 2022
@holmesworcester holmesworcester moved this from Backlog - Desktop & Backend to Blocked in Quiet Jun 17, 2022
@holmesworcester holmesworcester moved this from Blocked to Backlog - Desktop & Backend in Quiet Jun 17, 2022
@holmesworcester holmesworcester moved this from Backlog - Desktop & Backend to Next sprint in Quiet Jul 12, 2022
@holmesworcester holmesworcester moved this from Next sprint to Backlog - Desktop & Backend in Quiet Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
Quiet
Status: Backlog - Desktop & Backend
Quiet
Backlog - Desktop & Backend
Milestone
No milestone
Development

No branches or pull requests
1 participant
@holmesworcester