henryboldi/felony

Windows SmartScreen warning (unsigned software issue)

Open

#31 opened on Jul 4, 2016

View on GitHub
 (1 comment) (3 reactions) (1 assignee)JavaScript (155 forks)batch import
bughelp wanted

Repository metrics

Stars
 (3,486 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

https://i.imgur.com/opPlZ5X.png

https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-smartscreen-extended-validation-ev-code-signing-certificates/

"Best Practices" , get an EV cert is a quick fix.

Suggest that you don't go "life" i.e. promote to lifehacker or whatever, before this is fixed.

Contributor guide

Research direction
Research how to obtain an Extended Validation (EV) code signing certificate and sign the Windows build. Steps: 1) Obtain an EV certificate from a trusted CA. 2) Configure the build pipeline to sign the executable. 3) Test the signed build on Windows to ensure SmartScreen warning is gone.
Tech stack
javascriptelectron
Domain
securitydesktop
Issue type
Security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Windows development environmentCode signing certificate knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70