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

Windows Defender false positive 🙄 detects my golang product as a Trojan Wacatac!ml😈 #442

Closed
kachick opened this issue Mar 7, 2024 · 2 comments · Fixed by #443
Closed

Comments

@kachick kachick added the wontfix label Mar 7, 2024
@kachick kachick added this to 🛸 Mar 7, 2024
@github-project-automation github-project-automation bot moved this to To do in 🛸 Mar 7, 2024
@kachick
Copy link
Owner Author

kachick commented Mar 7, 2024

How CI this 🤔 actions/runner-images#855

kachick added a commit that referenced this issue Mar 7, 2024
Partially revert 8d23e76 to debug #442
@kachick kachick changed the title Windows Defender false positive 🙄 detects my packages as a Trojan Wacatac!ml😈 Windows Defender false positive 🙄 detects my golang product as a Trojan Wacatac!ml😈 Mar 7, 2024
kachick added a commit that referenced this issue Mar 7, 2024
I with this is not the cause of #442
@kachick kachick mentioned this issue Mar 7, 2024
kachick added a commit that referenced this issue Mar 7, 2024
* Run Windows Defender for Go product in CI except Dynamic Signatures
* Merge duplicate compiling Go workflows
* Note as comment in the new Windows action for how to dig or fight with Windows Defender
* Reinstall the Go compiler in Windows

I couldn't complete the first purpose, but this closes #442 for now.
@github-project-automation github-project-automation bot moved this from To do to Done in 🛸 Mar 7, 2024
@kachick
Copy link
Owner Author

kachick commented Mar 23, 2024

Kopia had same problem, Microsoft doesn't like golang... 👀 kopia/kopia#3410

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant