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

DPI vs. v2ray #2107

Closed
ghost opened this issue May 18, 2023 · 6 comments
Closed

DPI vs. v2ray #2107

ghost opened this issue May 18, 2023 · 6 comments

Comments

@ghost
Copy link

ghost commented May 18, 2023

I wonder if you have seen this repo and what is your idea about this repo?

https://github.com/rickyzhang82/V2Ray-Deep-Packet-Inspection

@ZhuangJiayu
Copy link

照你们这个翻github的速度,我要是GFW开发者我能高兴死,天天蹲在这个repo的issue里找各位老哥发现的检测方法,工作也太简单了。

@ZhuangJiayu
Copy link

你们伊朗兄弟们能不能懂得低调一点,别看到个东西就满世界宣传。

@ghost
Copy link
Author

ghost commented May 18, 2023

你们伊朗兄弟们能不能懂得低调一点,别看到个东西就满世界宣传。

I think you are missing some important points.
First, it's already on the internet and it only takes to search v2ray+DPI.
Second, if v2ray was working fine no one would bother to see what could be the problem. So, I assume GFW already knows about this and maybe it has implemented it.
Third, author clearly says he has reached out to v2ray developers (don't know if he has reached to xray devs). However, he had no answer.

@mega-optimus
Copy link

If the claim is true, i think it's an opportunity to integrate similar models into testing pipeline, to make the protocol truely anonymous.

@ghost
Copy link
Author

ghost commented May 18, 2023

If the claim is true, i think it's an opportunity to integrate similar models into testing pipeline, to make the protocol truely anonymous.

All of the tests had been done before utls adoption. Therefore, I was wondering if devs have tested these after utls adoption.

@RPRX
Copy link
Member

RPRX commented May 19, 2023

  1. 这个东西,早就见过,用深度学习的方式来做流量分类,可以,但有个小问题是,可解释性比较差,参数量越大越难解释
  2. 我清楚地知道所有已知协议的问题,请各位牢记,我有 N 种方式精准识别所有已知协议,这里的东西在我看来都只是玩具

@RPRX RPRX closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants