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

v1.3.48 flagged as trojan by windows #366

Closed
krish-gh opened this issue Oct 20, 2022 · 5 comments
Closed

v1.3.48 flagged as trojan by windows #366

krish-gh opened this issue Oct 20, 2022 · 5 comments
Labels
external The issue is due to external causes outside of Clink

Comments

@krish-gh
Copy link

krish-gh commented Oct 20, 2022

image

@krish-gh krish-gh changed the title v1 v1.3.48 flagged trojan by windows Oct 20, 2022
@krish-gh krish-gh changed the title v1.3.48 flagged trojan by windows v1.3.48 flagged as trojan by windows Oct 20, 2022
@pukkandan
Copy link

Duplicate of #34 #54 #138 #190 #298 #318

imo one of these issues should be pinned so that people dont keep asking the same

@theytaz
Copy link

theytaz commented Oct 20, 2022

Also curious, would it be triggered if the binaries are signed?

@chrisant996
Copy link
Owner

Also curious, would it be triggered if the binaries are signed?

That would depend on specific AV suites.

But since I'm not a company with multiple employees, it is not possible to get an EV code signing cert.

And even if it were possible, the certs cost several hundred dollars per year.

@chrisant996
Copy link
Owner

imo one of these issues should be pinned so that people dont keep asking the same

I'll create an issue and pin it. But it won't help as much as we'd hope: often people simply click New Issue without visiting the Issues page. For example, in the mridgers repo, many people have kept creating new issues despite an issue saying that the repo is dead and pointing at the new repo (with eye-catcher icons in its title, even).

@pukkandan
Copy link

My experience is that it somewhat helps. There will always be people who keep opening duplicates, but more people will look at pinned issues than closed issues

@chrisant996 chrisant996 added the external The issue is due to external causes outside of Clink label Oct 23, 2022
@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