Hacker News Reader

Comment by soheil | Hacker News Reader

Any reason why this wasn't implemented with telnet since no authentication is required?

SSH, once you (verify and) accept the first key exchange cannot be tampered with in transit, nor have the contents viewed by those sitting in-between.

However, I believe everyone's stdout/stderr is available to everyone, if everyone is the same user, and if that user has read access to /proc, so that confidentiality is only restricted those who access to the server.

It's also relatively trivial to set something up like this as SSH server supports auth delegation using PAM, and PAM can be configured with a single line using pam_succeed_if.so to disable auth only for a certain user.

In "public access single-app" cases like this, the user is generally connected to a restricted shell or other program which (… supposedly—this is very easy to get wrong if you're running anything that isn't specifically built for it) does not allow arbitrary executable access.

This is actually just a Go app which implements SSH using the Go standard library's SSH module. It's not like you're really SSH-ing into a server. See the source: https://github.com/hackclub/jobs

telnet is not shipped in the box on Windows and macOS, ssh is.

nc?

Windows ships with ssh now? Is that something new in win10+?

Yes, as of Windows 10 1809 the OpenSSH client is included. OpenSSH Server is available as a optional feature.

https://docs.microsoft.com/en-us/windows-server/administrati...

Both Windows and macOS come with telnet clients as part of their default installations.

However, there are many versions of Windows which do not ship with ssh.

Reply on news.ycombinator.com