database64128

swgp-go is a packet proxy. It's based on the client-server model, rather than the initiator-responder model used by the Noise protocol. The packets between a swgp-go client and server are...

Thank you for your work on the Docker images. One thing to note, you might want to change the Go version in Dockerfile to 1.21, as swgp-go might start requiring...

Instead of looking for ways to retrofit L3 packets into a L4 tunnel protocol like Shadowsocks, we can simply use a VPN to encapsulate IP packets and forward them using...

Or just switch to the new Shadowsocks 2022 protocol (#196). Shadowsocks 2022 provides full protection against replay and probes. My implementation also allows you to configure [how invalid requests are...

@dev4u What kind of custom header do you have in mind? Should subsequent reply still be random gibberish? Maybe instead of adding an option to allow `ReplyWithGibberish` to have a...

@dev4u Counterpoint: The censor can also block the port when the actual traffic does not match probing results. For example, the traffic over a Shadowsocks TCP port looks nothing like...

> when there are too many unknowns, doing nothing is somehow better than doing something. The current default is quite passive too. I just want to give users more options,...

@dev4u Fallback has been implemented in database64128/shadowsocks-go@bfe027008ad42b2c1434ad13a85a7d544cd5b302, and can be enabled by specifying an `"unsafeFallbackAddress"` in server config.

1. Both shadowsocks-go and shadowsocks-rust adheres to the spec, so they are fully compatible with each other. 2. Sounds totally unnecessary. 3. These "unsafe" features are intended for very specific...

> I propose allowing replay because why not. @Mygod https://gfw.report/blog/gfw_shadowsocks/