-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
utls packages in dpi iran #2219
Comments
(https://twitter.com/uo0sef/status/1668080992052027392) "It appears that the signatures of the 'utls' package are being detected by DPI (Deep Packet Inspection). In my code, when I use Chrome's signing feature, the client's request for 'utls' is flagged as a malformed packet, indicating an issue with the format or structure of the packet. However, when I use 'Android OkHttp', the same issue doesn't seem to be recognized." |
不过,现在我们对 uTLS 的使用方式,包括 uTLS 本身确实是存在一些问题,在把它们修复之前,我倾向于不说出来 |
Yes. some of the Signatures are detected by Iran's GFW and blocked (or interestingly, on some ISPs line MTN, the GFW makes the ping and jitter 5x worse!!!) |
我还是说一下吧,如果 仅观测 单个连接,对于绝大多数网站,我用 WireShark 看过 uTLS 的 Chrome 指纹是没问题的,但是:
不过这个 issue 显然不是上述问题,但好像也没说细节,如果确实有问题且能定位到细节,可以去给 uTLS 提 issue 或发 PR。 |
补充,序号对应:
|
RFC 8446你是哪裡能弄到正常人版本嗎?原版太難讀了,難讀不是因為英文,而是因為它是碎片化拼湊組織語言 |
我看的是原版,其实我觉得还好, |
你是用翻譯看的吧😜,就8446怪,RFC 9114的都挺正常聽好讀的 |
不是翻译,不过我没有通读过,我一般是先看目录或搜关键词,只挑感兴趣的部分看, |
搬运 https://t.me/projectXray/2058996
|
|
On behalf of myself and all my compatriots, I express my deepest gratitude to you If you need a server in Iran to test Iran's dpi, contact me |
@RPRX reality is being detected in Iran from almost 4 days ago, I don't know how they detect reality mechanism but I'm sure that I've configured my server exactly as you said in the repo(fallbacks,shortIDs, etc). it would be great if you take a look and give us some details so we can find a solution for this. we need your help. best regards |
Welp, seemingly this is a mirror issue to utls#193. In case people are still wondering, I'd make a clarification to the original issue. TL;DR: No, this error is not caused by a censor interfering uTLS. This "malformed HTTP response" error is due to client using HTTP/1.1 round-tripper on a TLS connection negotiated for HTTP/2 (via ALPN extension). And it has nothing to do with uTLS being identified or uTLS being blocked by any kinds of techniques. |
hi there
tnx for your great work
according to this tweet
https://twitter.com/uo0sef/status/1668080992052027392?t=cNSQWkDTozhMT9QVOaOHUg&s=19
there is an experiment done by uosof that proves dpi in iran can define utls sign packages !
please if it possible make a way for iranian folks that really need your help ❤️🙏
The text was updated successfully, but these errors were encountered: