discussion about uTLS

[young-zy]

This discussion mainly focuses on whether uTLS should be used in v2ray, and if the answer is yes, further discussion on configuration changes is needed(such as providing ability to let users determine whether to use uTLS or plain golang tls, or client hello type).

Over the past few days, I tried to implement uTLS into the v2ray transport, and I've completed an ugly implemention.

I've changed transport/tls.Client return a uTLSClient, and use only chrome latest finger print. (which should be able to configure in the future). domainSocket, kcp and tcp should rely on this feature.
Websocket and http uses NetDialTLSContext or DialTLSContext to handle logic of TLS connection rather than standard libray.It seems although the nextproto is set to http/1.1,the chrome latest fingerprint connects using http2 which causes failure, so I used randomized fingerprint without ALPN.
Also QUIC and gRPC Libs used in transport did not expose their TLS connections, so no modifications was made.

you may check the code changes in here