Feature Request: Support for VLESS REALITY Protocol
Hi cfal, First of all, thank you for creating and maintaining shoes! It's a powerful and versatile proxy server with an impressive set of supported protocols. I've been reviewing the documentation (CONFIG.md, README.md) and the provided examples, but I couldn't find any information about support for the VLESS REALITY protocol. Is this feature currently supported? If not, are there any plans to add it in the future? Motivation The REALITY protocol has become a very popular and effective method for censorship circumvention in the Xray/sing-box ecosystem. Its main advantage is that it eliminates the need for a domain name and a TLS certificate on the server by "borrowing" the TLS identity of a real, high-traffic website. This makes the proxy server extremely difficult to detect and block, as its TLS fingerprint is identical to that of a legitimate site. While shoes supports other excellent obfuscation methods like ShadowTLS v3 (which is great!), REALITY offers a unique combination of stealth and operational simplicity that would be a fantastic addition to the project's capabilities. Question If REALITY is not currently supported, I would like to formally request it as a new feature. Could you please share if this is on your roadmap? On the off-chance that it is supported and I missed it in the documentation, could you please provide an example configuration? I would expect to see fields in the vless protocol block similar to Xray's configuration, such as publicKey, privateKey, shortId, and dest. Thank you for your time and for the great work on this project. Looking forward to your response.
I've previously looked into this and it seems like we could reuse some of the existing TLS parsing from ShadowTLS. will investigate further when i have time.
I've previously looked into this and it seems like we could reuse some of the existing TLS parsing from ShadowTLS. will investigate further when i have time.
Hi cfal, Did you have chance to take a look on this? Please share with us what is your idea
This is now supported in v0.2.0