Hacker News Reader

Comment by el_isma | Hacker News Reader

Or just use tmux with multiple attached users?

Granted, this solution let's you give ssh access to anywhere, but usually if I want to share a terminal, it's on a server the other person has access to.

View on HN

I often use tmate [1] to do this, as it simplifies some of the fiddly bits and allows granting another user temporary access without granting them credentials (eg ssh key or username/password).

[1] https://tmate.io/

You probably shouldn't use tmate inside of most corps, your security team might be unhappy with bypassing network controls.

I'd be keen to hear why tmate isn't a good idea in terms of security.

As I understand it, the use of tmate is not so different from physically sitting next to a colleague and both of you taking the hot-seat with the computer.

Is the vulnerability around sending a shell to tmate.io? If so, I believe there is also an option to host the software on your own server.

You don’t see the difference between: 1) allowing anyone on the Internet to use an ssh shell on an internal server that’s protected by authentication and firewalls, vs 2) someone you know, who has already been granted physical access to your location, and likely already has a security clearance as well as undergone interviews, training, and other security checks?

Seems like a false dichotomy to me. In both cases you illustrated, I would actually be pairing with someone I know.

teamviewer enters the chat

... or screen, and you really just need a server both users have access to, and can reach the server you want to hack on together.

Most corporate networks won't allow you to open ports on your machine without approval. Solutions like tmate (awesome btw!) don't work because they're filtered.

I use tmux with a reverse ssh to a VM in our cloud and then a colleague can forward ssh to the VM.

"tmate is useful as it goes through NATs and tolerate host IP changes. Accessing a terminal session is transparent to clients as they go through the tmate.io servers, acting as a proxy. No authentication setup is required, like setting up ssh keys."

Corporate can't block outgoing traffic on well-known ports without user impairment, even with MITM certificates in place HSTS solves that security hole making outbound 443 quite open in most networks.

EDIT: tmate uses SSH as outbound transport, just like you are.

MITM certs are in place, yes. I suspected DNS lookup is denied, but that also works.

Not sure why my client is not connecting, if ssh is the outbound transport, perhaps it's because port 22 is blocked for non-network addresses?

Should be fine if you host your own tmate server.

I prefer byobu as a UI, but for sure this is way simpler than the post.

AFAIK byobu is just a theme for tmux or screen.

Hence calling it a UI, but yes, you are right.

Reply on news.ycombinator.com