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 (3,486 stars) (155 forks)batch import
bughelp wanted

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

Tech stack
javascript
Domain
securitydesktop
Issue type
security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Windows environmentEV code signing certificate
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests obtaining an Extended Validation (EV) code signing certificate to avoid the Windows SmartScreen warning. Research into using free or low cost options for open source projects, such as Microsoft's SignTool or Azure Key Vault, is needed. Additionally, the repository's build process should be configured to sign the executable during release.