We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Windows
Try to download cli53-windows-386.exe from the repo.
Download and run file.
Blocked by Windows Security as a Trojan:Win32/Occamy.C.
If I manually allow the file, it gets quarantined by Malwarebytes as a Generic Malware/Suspicious.
I need to then white list the file to run.
Yes
No
The text was updated successfully, but these errors were encountered:
+1 - I can confirm that I have this issue as well.
Sorry, something went wrong.
VirusTotal shows that 30 security vendors think this binary is malicious (link is for the 0.8.18 release): https://www.virustotal.com/gui/file/bbf05a84f37b4f692cae980bc8979e3a2f34ed41c8a131319751e438a0291a3a/detection
Is this project distributing malware?
We are certainly not distributing malware.
I do not build the releases - they are automatically built with goreleaser and uploaded from Github Actions.
The build process is entirely transparent / open for verification - you can see the last run that generated the 0.8.18 release here: https://github.com/barnybug/cli53/runs/1716819301?check_suite_focus=true
Additionally you can verify any of the checksums after you have downloaded the binaries for extra caution.
No branches or pull requests
Issue type
cli53 version (cli53 --version)
OS / Platform
Windows
Steps to reproduce
Try to download cli53-windows-386.exe from the repo.
Expected behaviour
Download and run file.
Actual behaviour
Blocked by Windows Security as a Trojan:Win32/Occamy.C.
If I manually allow the file, it gets quarantined by Malwarebytes as a Generic Malware/Suspicious.
I need to then white list the file to run.
Have you checked if the documentation has the information you require?
Yes
Could you contribute a fix or help testing with this issue?
No
The text was updated successfully, but these errors were encountered: