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

1.1.8 and 1.1.11 detected as threats by Symantec #34

Closed
zrma opened this issue Dec 22, 2020 · 4 comments
Closed

1.1.8 and 1.1.11 detected as threats by Symantec #34

zrma opened this issue Dec 22, 2020 · 4 comments
Labels
external The issue is due to external causes outside of Clink

Comments

@zrma
Copy link

zrma commented Dec 22, 2020

Versions 1.1.8 and 1.1.11 are detected as threats by Symantec.

image

image

thank you.

@chrisant996
Copy link
Owner

There's not really anything I can do about false positives in anti virus tools.

I can't read any of the text in the screen shots, so if there's important information in them maybe someone could translate.

@chrisant996 chrisant996 added the wontfix This will not be worked on label Dec 23, 2020
@zrma
Copy link
Author

zrma commented Dec 23, 2020

ok, thank you for your answer.

@chrisant996 chrisant996 added external The issue is due to external causes outside of Clink and removed wontfix This will not be worked on labels Jun 8, 2021
@s-kocher
Copy link

s-kocher commented Jun 29, 2021

Recently at work, I saw recent version of Clink be blocked by antivirus, Symantec again (Symantec Endpoint Protection aka SEP).
It was because of their reputation scanner : https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-protection/all/Glossary/file-reputation-v32546090-d49e18645.html

We get this kind of alert :

Scan type: Auto-Protect Scan
Event: Security Risk Found!
Security risk detected: WS.Reputation.1

This can be fixed by filling the false positive Symantec form :
https://symsubmit.symantec.com/
https://knowledge.broadcom.com/external/article/178170/submit-false-positives-detected-by-endpo.html

I already did that for proxy software, after few days, it was fine : genotrance/px#62

Better wait there are less releases to submit to any antivirus company that reject clink the latest stable binary.

@garoto
Copy link

garoto commented Jun 29, 2021

If this "flagging" starts to happen more often with Symantec and other snakeoil "AV suites", then it'll be a never ending struggle, new binaries after new binaries. It all sounds almost like a shakedown scheme.

@chrisant996 chrisant996 closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external The issue is due to external causes outside of Clink
Projects
None yet
Development

No branches or pull requests

4 participants