[GH-ISSUE #2539] 360安全提示可否取消 #2017

Closed
opened 2026-05-05 13:18:20 -06:00 by gitea-mirror · 9 comments
Owner

Originally created by @liuhaogui on GitHub (Aug 20, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2539

windows环境下载release直接报毒。

添加信任,运行frpc一样报毒。 有什么办法解决么?谢谢

1629419022457

Originally created by @liuhaogui on GitHub (Aug 20, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2539 windows环境下载release直接报毒。 添加信任,运行frpc一样报毒。 有什么办法解决么?谢谢 ![1629419022457](https://user-images.githubusercontent.com/47664337/130160354-1322169c-db0f-4e42-89c9-ae7d9e9da0e8.jpg)
gitea-mirror 2026-05-05 13:18:20 -06:00
Author
Owner

@jamy325 commented on GitHub (Aug 20, 2021):

卸载360

<!-- gh-comment-id:902360366 --> @jamy325 commented on GitHub (Aug 20, 2021): 卸载360
Author
Owner

@liuhaogui commented on GitHub (Aug 20, 2021):

先提交误报,等待反馈

有没有经验的大佬。 给下方向。
开发人员都懂肯定多半不会用360。 如果面向用户的东西就很有必要考虑小白用户了。是需要解决的。

1、360审核
2、加壳免杀

有没别的扫描方向,希望指教谢谢。

<!-- gh-comment-id:902382047 --> @liuhaogui commented on GitHub (Aug 20, 2021): 先提交误报,等待反馈 有没有经验的大佬。 给下方向。 开发人员都懂肯定多半不会用360。 如果面向用户的东西就很有必要考虑小白用户了。是需要解决的。 1、360审核 2、加壳免杀 有没别的扫描方向,希望指教谢谢。
Author
Owner

@liangzx96 commented on GitHub (Aug 22, 2021):

这玩意儿做的事情就是端口转发呀,对于360从行为上来说确实和木马没啥区别吧,要么就是给360缴投名状,要不然就是对抗杀软,这两个都不怎么讨好

<!-- gh-comment-id:903306459 --> @liangzx96 commented on GitHub (Aug 22, 2021): 这玩意儿做的事情就是端口转发呀,对于360从行为上来说确实和木马没啥区别吧,要么就是给360缴投名状,要不然就是对抗杀软,这两个都不怎么讨好
Author
Owner

@jiqing112 commented on GitHub (Aug 25, 2021):

360和腾讯管家都会有提示,卸载就好了

<!-- gh-comment-id:905425450 --> @jiqing112 commented on GitHub (Aug 25, 2021): 360和腾讯管家都会有提示,卸载就好了
Author
Owner

@tylzh97 commented on GitHub (Sep 6, 2021):

重复的问题 #1204
golang写的程序在windows下经常报毒,golang官网faq列表中给出如下回复:https://golang.org/doc/faq#virus

<!-- gh-comment-id:913707459 --> @tylzh97 commented on GitHub (Sep 6, 2021): 重复的问题 #1204 golang写的程序在windows下经常报毒,golang官网faq列表中给出如下回复:https://golang.org/doc/faq#virus
Author
Owner

@github-actions[bot] commented on GitHub (Oct 7, 2021):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:937347784 --> @github-actions[bot] commented on GitHub (Oct 7, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Author
Owner

@liuhaogui commented on GitHub (Oct 9, 2021):

改几行重新build下就可以了。

<!-- gh-comment-id:939263901 --> @liuhaogui commented on GitHub (Oct 9, 2021): 改几行重新build下就可以了。
Author
Owner

@liuhaogui commented on GitHub (Oct 9, 2021):

/close

<!-- gh-comment-id:939263967 --> @liuhaogui commented on GitHub (Oct 9, 2021): /close
Author
Owner

@github-actions[bot] commented on GitHub (Nov 10, 2021):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:964669450 --> @github-actions[bot] commented on GitHub (Nov 10, 2021): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#2017
No description provided.