-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Add uTLS Support into V2Ray's TCP and WebSocket transport #2219
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
Conversation
Codecov ReportBase: 39.37% // Head: 39.32% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2219 +/- ##
==========================================
- Coverage 39.37% 39.32% -0.05%
==========================================
Files 616 624 +8
Lines 36738 36914 +176
==========================================
+ Hits 14465 14517 +52
- Misses 20688 20804 +116
- Partials 1585 1593 +8
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
(Still need to make it fail-close and crash when TLS setting is invalid for transport or mode.)(Done) |
a93bb86
to
43ae270
Compare
43ae270
to
94aa3df
Compare
Hello! Is uTLS compatible with "pinnedPeerCertificateChainSha256" of "tlsSettings" ? |
Sorry, as of now, pinnedPeerCertificateChainSha256 is not supported in uTLS yet. |
Thank you for letting me know. |
This is a pull request with the necessary change to add uTLS Support into V2Ray's TCP and WebSocket transport.
You can enable this function with outbound settings like this. The tlsConfig config field is exactly the same as the TLS setting.
It is worth noting, to make sure WebSocket Transport works as expected, ALPN extension was overwritten. This means it may generate additional identification information than uTLS's default configuration(with acknowledgment to The Parrot is Dead paper).
Thanks @HirbodBehnam for the ALPN workaround.