-
-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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 20H2 report Atosev!ml & Presenoker #2095
Comments
sorry, mis report The answer is here: |
Same err.And I'm deleted. |
I'm not sure what i can do to solve it since maybe it caused by golang. The reason is here #1204 (comment) . If anyone have a solution to avoid this problem? |
识别病毒是根据特征码的, 特征码的生成是每个杀毒软件的独门。 |
Files can be manually submitted to here to report an incorrect detection. But it might require doing so when every new version releases. |
@cnwangjihe Great! Thanks for you help. |
服务端被阿里云识别为黑客工具。 |
似乎和go版本有关,旧点版本正常 |
same for 0.35.0 amd64 binary. |
可能是交叉编译套壳的问题,用windows下go编译的使用和下载没用检测病毒的提示 |
|
@zsinba |
我觉得你说的不对。 |
@zsinba 直接upload 里面的frpc.exe 扫描一下 Symantec 可能就会报了。 对比看 linux编译的确实会被 Windows Defender 标记出来 ,(ESET 也标记了多个)。 |
这是上传的frpc |
@zsinba 这个exe 似乎通过了Windows defender 的扫描。 |
|
我觉得问题不在这, 杀毒软件通过特征码来判定是否是特征库里的文件。 从另一方面说,报病毒也没什么,加入白名单就行。 这个本来就是当反向代理用的。 杀毒软件 报这个也是为了用户安全,不然用户的电脑 端口暴漏了,自己也不清楚。 |
联系了ESET的病毒分析处,他们说就是因为发现frp有被黑客利用的迹象所以报毒。所以最初报hacktool,后来上报之后改成报riskware |
这理由, 服了 |
这个并不是没有发生过,putty都曾被当hacktool杀过 |
@sxu55 非常感谢帮忙跟踪这个问题,被黑客利用确实是一个问题,杀毒厂商和云服务商从出于用户安全的角度来说,对小白用户确实可能可以起到一定的保护作用。 我们能做的可能是将 Release 二进制的 MD5 同步上传,用户主动下载后自行校验,之后加入白名单。 |
对的,我认为这是最有效率的做法 |
Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close. |
前面我们没有在意报病毒,安装到一台内网的机器中了后,也有可能win2019 3389也可能有问题,结果一台机器的数据全部被加密了。 |
我根本下载都不能,不是给Edge或者Chrome打断,就是一下载来本地磁盘立刻被windows给隔离删除了。。。怎么搞 |
不用。 |
[REQUIRED] hat version of frp are you using
Version: 0.34 frpc
[REQUIRED] What operating system and processor architecture are you using
OS: Win
CPU architecture: Intel X64
[REQUIRED] description of errors
Windows 20H2 report Atosev!ml & Presenoker
confile
NA
log file
NA
Steps to reproduce the issue
Supplementary information
NA
Can you guess what caused this issue
NA
Checklist:
The text was updated successfully, but these errors were encountered: