shadowsocks-go VS Xray-core

@database64128 is concerned about the vulnerability introduced by the above. Another way to evade censorship is implemented in the database64128 fork of shadowsocks-go. Because the protocol is changed, it requires updating both client and server. "The unsafe stream prefix feature allows you to configure a pair of preshared cleartext prefixes for Shadowsocks 2022 streams. The prefixes are prepended to the request and response streams to trick simple firewalls. To use this feature, add unsafeRequestStreamPrefix and unsafeResponseStreamPrefix to both client and server blocks, and specify the prefixes in base64 encoding. The client and server must agree on the same pair of prefixes. On startup a warning message will be printed to tell you that using this feature taints the client and server." Precompiled binaries are available at https://github.com/database64128/shadowsocks-go/releases

- [xray](https://github.com/xtls/xray-core)

I have been researching VPN protocols that work in China and found that Xray [0] is the most recommended route to escape the GFW. An ideal VPN setup is one where packets appear as normal https traffic. Some VPN setups take it a step further and proxy the traffic through Cloudflare. Setting all this up is nowhere as easy as Wireguard. Coincidentally, I came across this project on Github earlier today which is an obfuscation proxy for Wireguard [1], but I haven't found any information about how well it works.

[0] https://github.com/XTLS/Xray-core

[1] https://github.com/database64128/swgp-go

Take a look at this thread as an example: https://github.com/XTLS/Xray-core/issues/2059

Also look at the Issues and/or Discussions tabs at https://github.com/XTLS/Xray-core and follow the link to the Telegram support group.