v2ray-core VS shadowsocks-go

Hey there! Lots of experience with this having lived in China for 2 years. I recommend you look into xray-core or v2ray.

https://github.com/v2fly/v2ray-core

https://github.com/XTLS/Xray-core

Here are my configs: https://github.com/acheong08/notes/tree/main/xray

cd ~ wget https://github.com/v2fly/v2ray-core/releases/download/v5.7.0/v2ray-linux-64.zip sudo apt install -y unzip unzip v2ray-linux-64.zip cp geoip/output/dat/* . ./v2ray uuid

If the changing por trick work you can try shadowsocks or v2ray.

Normal VPNs that you can see ads all over the place like N*rdVPN won't work, period. The correct way is to rent a few servers from different providers, make sure their ips are not blocked, and build your own V2Ray or Trojan service first. The Chinese gov will not be able to distinguish your Trojan traffic from ordinary https traffic, so the only thing that's sus to them would be the fact that all your traffic goes to one foreign ip, but I've been doing it for a few years without officials knocking on my door so yeah I think it will work for you as well. I don't take responsibility tho, do your research.

Given that every other client is mostly using https://github.com/v2fly/v2ray-core that can be compiled for every architecture/platform that Outline client supports, maybe it's worth investing time into allowing it as a backend. It can even be used for pure shadowsocks since it's for sure more updated than the old golang shadowsocks implementation.

v2Ray: https://v2fly.org

@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