No Encryption? about hev-socks5-tproxy HOT 13 CLOSED

Yes, the standard socks5 proxy protocol is easy to detected by GFW. This is just a transparent proxy client that communicate with socks5 compatible server. We can use any obfuscation protocol for cross-border communication.

from hev-socks5-tproxy.

Would you consider adding a Websocket and TLS1.3 layer on top of the socks5 protocol?

from hev-socks5-tproxy.

How to work? What can this solve?

from hev-socks5-tproxy.

something like vmess+websocket+tls+nginx. replace vmess with socks5, you'll have user authentication via socks5 between server and client, as well as strong encryption and a standard https fingerprint, pretty safe.

from hev-socks5-tproxy.

Sounds good, I have a private project that implements a confusing protocol and seems works fine. I think it's better to implement a socks5 compatible server based on WebSocket and TLS, and use it in combination with this project?

from hev-socks5-tproxy.

Yeah, good idea, you can put the sock5 server behind Nginx. Other confusing protocol won't live long.

from hev-socks5-tproxy.

Any plan to add PURE tproxy support, so only mangle table is needed, and both udp and tcp are supported.

Reference:
https://www.kernel.org/doc/Documentation/networking/tproxy.txt

from hev-socks5-tproxy.

I found that this program is very useful when work with Trojan

from hev-socks5-tproxy.

Any plan to add PURE tproxy support, so only mangle table is needed, and both udp and tcp are supported.

Reference:
https://www.kernel.org/doc/Documentation/networking/tproxy.txt

IIRC, the TPROXY target needs privilege capabilities.

from hev-socks5-tproxy.

Any plan to add PURE tproxy support, so only mangle table is needed, and both udp and tcp are supported.
Reference:
https://www.kernel.org/doc/Documentation/networking/tproxy.txt

IIRC, the TPROXY target needs privilege capabilities.

Yes, that's correct, setcap can get things done so that No root privilege is needed to listen as tproxy.

from hev-socks5-tproxy.

Any plan to add PURE tproxy support, so only mangle table is needed, and both udp and tcp are supported.
Reference:
https://www.kernel.org/doc/Documentation/networking/tproxy.txt

IIRC, the TPROXY target needs privilege capabilities.

Yes, that's correct, setcap can get things done so that No root privilege is needed to listen as tproxy.

This project is run as a module in JVM on Android, not a standalone process, may be can not set caps for it.

from hev-socks5-tproxy.

OK, maybe add an option to listen as TPROXY?

from hev-socks5-tproxy.

OK, maybe add an option to listen as TPROXY?

Yes.

from hev-socks5-tproxy.