Why aren't we using SSH for everything? (2015)(shazow.net)
shazow.net
Why aren't we using SSH for everything? (2015)
https://shazow.net/posts/ssh-how-does-it-even/
9 comments
A thing I ran into is there are no virtual hosts in SSH, i.e. you can't have an SSH server at happy.example.org and ecstatic.example.org if they're both the same IP address. There was a patch for this but support waned. It's a huge blocker.
For any specific use you could build something on top of it to deal with that. For example if you go with the last idea in the article and build http over ssh then your server just looks at the headers.
You would not have separate certs for each subdomain but is that a problem? arguably more convenient.
You would not have separate certs for each subdomain but is that a problem? arguably more convenient.
I know a commercial product isn't necessarily the solution, but I just love Tailscale. It makes sshing around absurdly easy and clean.
There is also the open source headscale, which I haven't used but seems to be well respected.
There is also the open source headscale, which I haven't used but seems to be well respected.
> It’s lacking a notion of virtual hosts, or being able to serve different endpoints on different hostnames from a single IP address.
this is the answer. but fantastic read of an article
this is the answer. but fantastic read of an article
A dwarf fortress style mmorpg played over SSH would be incredible
I guess the answer is UI, which clearly the author didn't mention
You can use an UI application remotely via ssh via X11 forwarding.
But, at least over wi-fi, I've found it to be too slow to be useful.
But, at least over wi-fi, I've found it to be too slow to be useful.
there were some attempts (waypipe) to get a similar thing working on Wayland
Aren't we?