Stealth: SOCKS Connection Refactor about stealth HOT 2 CLOSED

The API of the SOCKS wireformat has been changed.

• The @status header is now a Number, not a String anymore
• The @version header was pointless, as SOCKS5 is the protocol version anyways.
• The @connect-tunnel event's callback signature changed, especially the callback(status, address, socket) signature.

These things have to be changed accordingly in the new Proxy implementation.

from stealth.

The SOCKS Connection API has changed. Now the SOCKS Connection does not fire a @tunnel event and also no @connect event anymore, in order to make the usage of external network protocols easier.

DNSH based Connections have to use the dnsh:// protocol scheme in the URL from now on, otherwise there'll be a conflict with https://. But, this allows now to generically route almost all network protocols through TOR with ICMP and DNS being the exceptions as they're not TCP based protocols.

TOR's SOCKS proxy doesn't support UDP in a failsafe manner (and therefore technically is a SOCKS4 proxy featureset, not SOCKS5, but who cares!?). Needs further debugging what's missing and why TOR's proxy fails with that use case.

• Debug why UDP based connections fail with TOR SOCKS Proxy, but not with others.

from stealth.