SSH has no Host header
11 points
2 hours ago
| 2 comments
| blog.exe.dev
| HN
▲
rahimnathwani
13 minutes ago
[-]
I started reading this thinking 'why not just use different port numbers' but I came away convinced that the problem was worth solving and their solution is neat.
reply
▲
eqvinox
10 minutes ago
[-]
> came away convinced that the problem was worth solving

What convinced you? I don't see it. The user is using SSH, if they can't pass a -p option (or type it in a GUI) to their SSH client they won't be able to do much with the shell they're getting either?

reply
▲
rahimnathwani
6 minutes ago
[-]
I like that you can just use the hostname for web and ssh, without considering that the same IP address isn't exclusively yours.

And, sure, you can add a -p option. But if you have 20 VMs (which is how many come with their basic plan) you'd have to remember all the different port numbers.

(I'm not in the target market for their service.)

reply
▲
cweagans
52 minutes ago
[-]
That's a really neat solution. Does that mean one of the constraints you'd have to impose is that a given customer can only have as many VMs as there are addresses in the block of IPs that you own? If they tried to create another one past that, it seems like you'd have a bit of a problem on your hands - but then again, maybe that number is so high that you're not likely to run into that edge case?
reply
▲
rahimnathwani
5 minutes ago
[-]
Their docs say the enterprise plan comes with a max of 30 VMs.
reply