-
Notifications
You must be signed in to change notification settings - Fork 62
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
shadow-tls implementation #321
Comments
interesting. there's also discussions about this topic here refraction-networking/utls#103 |
if you don't mind, you can put the forked repo under this org. |
Got it |
Yep, it's similar to the patch mentioned in this issue |
Motivation
The shadow-tls protocol may be one of safest protocol now? (I've used the shadow-tls-v3 for a long time, it's pretty stable)
Current implementation in other repos
Status quo:
what we need to do
I had fully implement this protocol in my local environment and had it fully tested, however, i don't know what's the best way to handle the dependency of the hacked rustls & tokio-rustls: should i maintain the code by myself, or should we create a organization, and move the forked repos(rust-tun, netstack-lwip .etc ) to it?
The text was updated successfully, but these errors were encountered: