|
|
|
|
|
by lillecarl
1526 days ago
|
|
"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. |
|
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?