Return to Answer

You are creating SOCKS proxy with tunnel from your local computer to your localhost. But from the localhost to the target server (example.com), the data re not encrypted anymore. Diagram:

[browser] ==encrypted SOCKS channel== [localhost] ==HTTP request== [example.com]

You can encrypt this SOCKS proxy only point-to-point (from your client to your ssh server) and not further. The HTTP server expects normal HTTP requests and not SOCKS messages.

If you would like to be safe from the snooping in the hotel or somewhere else, you need to have an SSH server in some location other than on your computer (e.g. VPS, home). But it won't protect you from snooping "around" the other computer.

You are creating SOCKS proxy with tunnel from your local computer to your localhost. But from the localhost to the target server (example.com), the data re not encrypted anymore. Diagram:

[browser] ==SOCKS== [localhost:1080] ==SSH== [localhost] ==HTTP== [example.com]

(where only the SSH part, meaning SSH tunnel, is encrypted)

You can encrypt this SOCKS proxy only point-to-point (from your client to your ssh server) and not further. The HTTP server expects normal HTTP requests and not SOCKS messages.

If you would like to be safe from the snooping in the hotel or somewhere else, you need to have an SSH server in some location other than on your computer (e.g. VPS, home). But it won't protect you from snooping "around" the other computer.

You are creating SOCKS proxy with tunnel from your local computer to your localhost. But from the localhost to the target server (example.com), the data re not encrypted anymore. Diagram:

[browser] ==encrypted SOCKS channel== [localhost] ==HTTP request== [example.com]

You can encrypt this SOCKS proxy only in point-to-point (from your client to your ssh server) and not further. The HTTP server expect normal HTTP requests and not SOCKS messages.

If you would like to be safe from the snooping in the hotel or somewhere else, you need to have SSH server in some other location than on your computer (VPS, home). But it wont protect you from snooping "around" the other computer.

You are creating SOCKS proxy with tunnel from your local computer to your localhost. But from the localhost to the target server (example.com), the data re not encrypted anymore. Diagram:

[browser] ==encrypted SOCKS channel== [localhost] ==HTTP request== [example.com]

You can encrypt this SOCKS proxy only point-to-point (from your client to your ssh server) and not further. The HTTP server expects normal HTTP requests and not SOCKS messages.

If you would like to be safe from the snooping in the hotel or somewhere else, you need to have an SSH server in some location other than on your computer (e.g. VPS, home). But it won't protect you from snooping "around" the other computer.

You are creating SOCKS proxy with tunnel from your local computer to your localhost. But from the localhost to the target server (example.com), the data re not encrypted anymore. Diagram:

[browser] ==encrypted SOCKS channel== [localhost] ==HTTP request== [example.com]

You can encrypt this SOCKS proxy only in point-to-point (from your client to your ssh server) and not further. The HTTP server expect normal HTTP requests and not SOCKS messages.

You are creating SOCKS proxy with tunnel from your local computer to your localhost. But from the localhost to the target server (example.com), the data re not encrypted anymore. Diagram:

[browser] ==encrypted SOCKS channel== [localhost] ==HTTP request== [example.com]

You can encrypt this SOCKS proxy only in point-to-point (from your client to your ssh server) and not further. The HTTP server expect normal HTTP requests and not SOCKS messages.

If you would like to be safe from the snooping in the hotel or somewhere else, you need to have SSH server in some other location than on your computer (VPS, home). But it wont protect you from snooping "around" the other computer.