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.

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

[2] Light wallet binaries quarantined by Windows10 Guard and Symantec due to WS.Reputation.1 #1259

Open
abitmore opened this issue Mar 4, 2018 · 13 comments
Labels
[3] Feature Classification indicating the addition of novel functionality to the design [4c] High Priority Priority indicating significant impact to system/user -OR- workaround is prohibitivly expensive

Comments

@abitmore
Copy link
Member

abitmore commented Mar 4, 2018

According to https://bitsharestalk.org/index.php?topic=26046.0 :

I downloaded the latest version for Windows desktop: https://bitshares.org/download/
But couldn't install it because Symantec AV detected a "WS.Reputation.1" threat...

For reference https://www.symantec.com/connect/forums/how-avoid-wsreputation1-error

Need to sign the binaries and/or submit them to Symantec and other AV companies for white-listing.

@wmbutler wmbutler added the [3] Feature Classification indicating the addition of novel functionality to the design label Mar 5, 2018
@wmbutler wmbutler added this to the 180401 milestone Mar 5, 2018
@wmbutler
Copy link
Contributor

wmbutler commented Mar 5, 2018

Placing in 180401

@wmbutler wmbutler changed the title Light wallet binaries quarantined by Windows10 Guard and Symantec due to WS.Reputation.1 [2] Light wallet binaries quarantined by Windows10 Guard and Symantec due to WS.Reputation.1 Mar 5, 2018
@abitmore
Copy link
Member Author

abitmore commented Mar 5, 2018

The thing we need to do NOW is to "submit the binaries to Symantec and other AV companies for white-listing."

Although we may add signatures from a future sprint.

@wmbutler
Copy link
Contributor

wmbutler commented Mar 6, 2018

I only added it to the next Sprint because the current sprint is PACKED!

@abitmore
Copy link
Member Author

abitmore commented Mar 6, 2018

So will anyone submit the latest PACKED binaries to Symantec and other AV companies for white-listing?

@abitmore abitmore added the [4c] High Priority Priority indicating significant impact to system/user -OR- workaround is prohibitivly expensive label Mar 6, 2018
@abitmore
Copy link
Member Author

abitmore commented Mar 6, 2018

This is high priority.

@abitmore
Copy link
Member Author

abitmore commented Mar 6, 2018

More info in this thread: https://bitsharestalk.org/index.php?topic=26047.0

@clockworkgr
Copy link
Member

Can the binaries be submitted by anyone/devs? Or must there be some legal entity (ie vendor) making a formal request? If it's the second case we would require the foundation's involvement.

@wmbutler
Copy link
Contributor

wmbutler commented Mar 6, 2018

@xeroc ?

@happyconcepts
Copy link
Contributor

AFAIK you can now only tell symantec about false positives; they don't white list anymore? https://submit.symantec.com/whitelist/isv/

@svk31
Copy link
Contributor

svk31 commented Mar 9, 2018

I did buy a certificate for Windows a couple months back, but it's taking forever to get validated as my UPIK entry was missing some information. I've since updated it but it's taking a while for them to reflect the updates on their site. Once it's updated I'll be able to sign the windows binaries.

@wmbutler wmbutler modified the milestones: 180401, 180415 Apr 1, 2018
@sschiessl-bcp
Copy link
Contributor

@svk31 did the update go through?

@wmbutler wmbutler modified the milestones: 180418, 180501 Apr 18, 2018
@wmbutler wmbutler removed this from the 180501 milestone May 12, 2018
@svk31
Copy link
Contributor

svk31 commented Jul 27, 2018

It did not, trying again now

@wmbutler wmbutler modified the milestones: 180803, 180801, 180815 Jul 31, 2018
@wmbutler wmbutler modified the milestones: 180815, 180905 Aug 26, 2018
@wmbutler wmbutler modified the milestones: 180905, 180919 Sep 13, 2018
@wmbutler wmbutler modified the milestones: 180919, 181003 Sep 25, 2018
@wmbutler wmbutler removed this from the 181003 milestone Sep 25, 2018
@startailcoon
Copy link
Contributor

@svk31 Ping?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[3] Feature Classification indicating the addition of novel functionality to the design [4c] High Priority Priority indicating significant impact to system/user -OR- workaround is prohibitivly expensive
Projects
None yet
Development

No branches or pull requests

7 participants