undefined | Better HN

0 pointsskrebbel12y ago0 comments

So we tunnel everything through 80/443, and then proxies are going to deep packet inspect that, and selectively block some over-http protocols, so we're going to tunnel stuff through a more innocuous looking protocol over HTTP, and tunnel through the tunnel through the tunnel through the tunnel.

I propose OpenVPN/SOCKS/WebSocket/HTTP/TCP/IP as the new de-facto standard connection protocol. Maybe we can FTP through that VPN connection some time, please wait while I cook up a JavaScript FTP/OpenVPN/SOCKS/WebSocket/HTTP/TCP/IP client.

0 comments

4 comments · 2 top-level

gtirloni12y ago· 2 in thread

Looked like a good idea until you mentioned JavaScript. Bummer.

tylerlh12y ago

If you're so against a js client, you could certainly whip one up in another language...

gtirloni12y ago

Whoosh...

EDIT: A OpenVPN/SOCKS/WebSocket/HTTP/TCP/IP is a terrible idea and I'm assuming it was meant as a joke. Thus, the addition of Javascript to the comment makes no difference at all. Thus, my comment was intended as a joke since it's irrelevant (again) in which language a bad proposal is implemented.

There, you took all the fun out of it. Happy? ;-)

4 more replies

nawitus12y ago

Every 5 years the concept of the application port will be re-invented at the higher level of the stack.

j / k navigate · click thread line to collapse