mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 22:01:23 -06:00
[GH-ISSUE #295] Binary installer blocked by Windows Defender SmartScreen #237
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#237
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @p0lm on GitHub (Apr 29, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/295
Operating Systems
Windows 10 Pro (version 1809)
Barrier Version
2.2.0
Steps to reproduce bug
The latest binary for Windows as downloaded from https://github.com/debauchee/barrier/releases/download/v2.1.2/BarrierSetup-2.2.0-Release.exe is blocked from running by Windows Defender SmartScreen.
@AdrianKoshka commented on GitHub (Apr 29, 2019):
Hrmm, this is, interesting.
@AdrianKoshka commented on GitHub (Apr 29, 2019):
Do you know what might cause this @noisyshape?
@noisyshape commented on GitHub (Apr 29, 2019):
Workaround: if you click on more info, you should see a button labeled "run anyway". If you don't see it, you will need to go into settings and change the SmartScreen setting from block to warn. I think warn is the default setting.
SmartScreen is a feature of Windows 8+ where an application's hash is sent to Microsoft and they say whether or not it's recognized. AFAIK this is strictly a matter of trust/reputation and involves no binary analysis so there isn't anything to be done about the installer itself. There are two ways for the installer to become recognized. First, it can be signed with an extended validity certificate which is more expensive and harder to get than a regular CA certificate. Second, Microsoft can see either the hash or the signing certificate enough and declare it recognized.
Note that SmartScreen involves sharing information with Microsoft and is something that some Barrier users will disable when they install Windows. This means both that some users won't have any experience with it and that Microsoft won't see the program hash as often as you might expect.
@AdrianKoshka commented on GitHub (Apr 30, 2019):
Really shouldn't do this (in my opinion).