I'm using a public library's WiFi and it seems I can't

HTTP tunnel

They blocked all ports besides 80 and 443.

>>61570911
Use a vpn that runs over 80 or 443. Then ssh through that

>>61570911
If you control the server you're sshing to you can just have it listen on 443. The shitty filters and firewalls on public wi-fi never bother inspecting the traffic to make sure it's actually HTTPS.

of course some residential ISPs disallow inbound 443 connections, so you might not be able to do that. worth a shot though

>>61571265
Is it even possible to tell HTTPS and SSH traffic apart?

File: 1500717347984.jpg (65KB, 389x400px) Image search: [Google]

65KB, 389x400px

>>61570911
Pwn your library's server and anonymously demand that they open ports 80 and 443 or else you brick the entire facility.

>>61571318
If you see the initial handshake, its easy. The dance the client and server do to set up encryption is totally different between SSH and TLS.