Jan 11, 2026

I've merged the last of the socks5 work. This generalizes the socket address handling so that both numeric and non-numeric (fqdn) addresses remain supported for both proxied and unproxied connections. Previously the presumption was that the far end of the connection was always resolvable to its IP address, which was used for certain aspects of peer tracking and logging. This is now generalized to non-IP names. This is necessary because under a proxy the name resolution should occur at the proxy, and the resolved IP address is not necessarily returned to the caller under socks5 (e.g. Tor proxy). Given this change address tracking is now based on the outgoing config::endpoint as opposed to the outgoing config::authority. And the resolved IP address remains used only for differentiating incoming connections.