Set up an ad hoc encrypted SOCKS proxy through an SSH server with ssh -D, then route arbitrary client traffic (browsers, curl, etc.) through it so requests appear to originate from the remote host.

Documented steps

1. Start the dynamic forward: `ssh -D 1080 <user>@<host>`. This opens a local SOCKS4/5 listener; syntax is `-D [bind_address:]port` and, by default, ssh binds it to the loopback address only.
2. For a non-interactive, backgrounded proxy, combine with -N (no remote command) and -f (background after auth, implies -n): `ssh -f -N -D 1080 <user>@<host>`.
3. Point a SOCKS-aware client at 127.0.0.1:1080. For curl, use `--socks5-hostname` (not plain --socks5) so hostname resolution also happens through the tunnel: `curl --socks5-hostname 127.0.0.1:1080 https://example.com`.
4. Configure a browser or OS proxy setting to use SOCKS host 127.0.0.1 port 1080, choosing a 'remote DNS' / SOCKS5h style option if offered, so hostnames resolve via the tunnel rather than locally.
5. Verify egress is via the remote host: `curl --socks5-hostname 127.0.0.1:1080 https://ifconfig.me` and confirm the printed IP is the remote host's, not your local IP.
6. Stop the proxy by killing the backgrounded process: `ps aux | grep '[s]sh -f -N -D 1080'` then `kill <pid>`.