Make SSH Use a SOCKS Proxy You Already Have

Use an existing SOCKS proxy as the transport for an SSH connection through a compatible ProxyCommand helper.

ssh -D creates a SOCKS listener; it does not select an existing one for SSH's own connection. With the OpenBSD implementation of nc, use a host entry in the SSH client configuration, such as ~/.ssh/config:

Host server-via-socks
    HostName ssh.example.com
    User alex
    ProxyCommand nc -X 5 -x 127.0.0.1:1080 %h %p

Invoke ssh server-via-socks. The helper contacts the SOCKS5 service on the SSH client's machine and requests the target host/port. SSH then performs normal host-key checking and user login inside the stream.

Check helper support before entering a proxy password. OpenBSD nc documents proxy authentication for HTTP CONNECT, not SOCKS authentication. A credential-protected SOCKS service may need another compatible helper. Keep the shared proxy's authentication instead of removing it to fit an unsupported client.

The destination sees the proxy's outward connection, while SSH verification still identifies the real server. Failure to reach its port occurs before SSH login; an accepted tunnel followed by key rejection belongs to SSH credentials.

The setting applies to this SSH connection. It does not configure browser traffic or every other application.

འབྲེལ་བའི་རྩོམ་ཡིག