4 ms·
I'm guessing the SSH session between me and my friend is not encrypted end-to-end because of proxies and what not in between?
by sigjuice 10y ago
I'm guessing the SSH session between me and my friend is not encrypted end-to-end because of proxies and what not in between?
- old-gregg 10y agoIt is properly encrypted: Your machine, being an SSH server, gets to decide who can login. The encryption works just with any normal SSH session: between the end user and the server (your machine). The cloud bridge running on https://teleconsole.com https://teleconsole.com simply acts as a proxy connecting sockets between two users who are behind NAT (without being able to decrypt). Disclaimer: I'm the author of Teleconsole. [edit: formatting]
- sigjuice 10y agoThanks for your reply. And apologies for my short attention span. I read "proxy", "NAT" and jumped to conclusions.
- deleted 10y ago[deleted]
- rileymat2 10y agoDoes it run as a proxy or does it just do the nat hole punching?
- old-gregg 10y agoThis page is good: http://gravitational.com/teleport/docs/architecture/ http://gravitational.com/teleport/docs/architecture/ The proxy accepts two incoming connections: from your server and from the client, then it bridges them and allows the client to negotiate an SSH handshake with the server.
- geofft 10y agoIt's very easy to get an authorized_keys file for a GitHub user account; just download (e.g.) https://github.com/geofft.keys https://github.com/geofft.keys . Presumably all this does is spawn a local SSH server with the appropriate authorized_keys file, and forward the TCP connection through the company's servers for NAT traversal. The actual connection is encrypted end-to-end.
- old-gregg 10y agoCorrect. Another thing it does is "merging" the incoming connections into the current bash session, so you can see each other type, the idea here was to work on the same machine together kind of like in Etherpad.