|
|
|
|
|
by vectorEQ
2714 days ago
|
|
i do want to be cynical:
sed -i -e 's/#Port 22/Port 443/g' /etc/ssh/sshd_config on a more serious note, as you described but maybe from a more grumpy person:
i don't think it's a great service, as it just compromises credentials by default while a normal configuration could solve it. if the server is also hosting some https website, then put it on an alternate ipv6 address (they are free if not cheap) and ssh into that. you only need to edit 2 files on your server for that to work :s why pay 5$ a month if you already have a capable server you are paying for?? the promise of not storing credentials etc. is nice, but if your servers are compromised it will be childsplay for efarious people to intercept them even if you didn't design that aspect to happen in the service design. |
|
There's also sslh, which can multiplex the same port by detecting whether the incoming connection is TLS or SSH, and forwarding appropriately. It's pretty cool: https://www.rutschle.net/tech/sslh/README.html
That said, I think this service is for people who need to use computers without ssh clients installed locally.