11–20 of 105 posts
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?
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.
Yeah, what a great idea, let random "cloud" services authenticate who gets to login to your machine!
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?
It's very easy to get an authorized_keys file for a GitHub user account; just download (e.g.) 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.
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?
It 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 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: formatti…
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?
It 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 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: formatti…
Yeah, what a great idea, let random "cloud" services authenticate who gets to login to your machine!
Being unconstructively snarky about a concept that another member of this forum has presented is both poor manners and defies the guidelines linked in the bottom of the page
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?
It 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 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: formatti…
Earlier quoted context omitted.
Being unconstructively snarky about a concept that another member of this forum has presented is both poor manners and defies the guidelines linked in the bottom of the page
Just making a critique of the concept. Didn't think that was against any guidelines.
"It seems like a big risk to allow a little-known cloud service to authorise SSH access to your laptop. What are the use cases for this? What do you need to be careful of?"
Earlier quoted context omitted.
It 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 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: formatti…
Does it run as a proxy or does it just do the nat hole punching?
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.
I don't have friends that know what SSH is. Just wonderful colleagues.