Implement AnyTLS client & server#2615
Implement AnyTLS client & server#2615nekohasekai merged 5 commits intoSagerNet:dev-nextfrom anytls:pr1.12
Conversation
|
Using sing-box's proprietary UoT protocol for UDP traffic doesn't seem to be an elegant approach for a new protocol, I suggest you create a built-in UoT protocol like trojan did instead, what do you think about this? |
|
You can see that naiveproxy does not support UDP at all. This shows that UDP is not particularly important. For L7 proxies, people have always thought that as long as UDP can be used, it will be fine. We are not a game accelerator. As for sing-box's UoT, I think it is already a de facto standard, and many Chinese proxy software supports it. Even if some software does not support it yet, it is not difficult to implement, as it is also a simple and clear protocol. |
|
It makes sense. Please create a tag for your library and we can continue. |
c641e64 to
af813c0
Compare
|
I seem to be missing something? It looks like your library is missing a license. |
|
This is just another boring proxy protocol implementation. I don't know which LICENSE I should use, what do you think? |
|
|
|
Even if someone doesn't care about the protocol and steals our code, and some people specifically choose protocols that can be used by closed-source software to expand their influence, we can choose to be serious. |
|
Please add a tag for the new license? This seems to be the last question. |
|
自问自答还挺有意思,单口相声讲的真好 |
#2611
Additional Notes:
wsright now, and I'm also not interested in dealing withfallbackright now.anytls/sing-anytlstoSagerNet/sing-anytls, then update the module name.