21–30 of 105 posts
1. Why would I want someone to ssh into my machine -- at least with the frequency that a service to help me do it is valuable?
2. How is this easier/better than saying 'hey bro whats your ssh pub id? -- eh.. do `cat ~/.ssh/id_rsa.pub`
Over all this seems like a tool that only super technical people would ever use, and for those people adding a key to authorized keys is trivial.
I'm confused and have a couple questions: 1. Why would I want someone to ssh into my machine -- at least with the frequency that a service to help me do it is valuable? 2. How is this easier/better than saying 'hey bro whats your ssh pub id? -- eh.. do `cat ~/.ssh/id_rsa.pub` Over all this seems like a tool that only super technical people would ever use, and for those people adding a key to authorized keys is trivia…
I'm confused and have a couple questions: 1. Why would I want someone to ssh into my machine -- at least with the frequency that a service to help me do it is valuable? 2. How is this easier/better than saying 'hey bro whats your ssh pub id? -- eh.. do `cat ~/.ssh/id_rsa.pub` Over all this seems like a tool that only super technical people would ever use, and for those people adding a key to authorized keys is trivia…
http://blog.endpoint.com/2009/09/gnu-screen-follow-leader.ht...
What kind of abuse prevention measures does this have in place? As it stands it looks like a super convenient way to scp garbage into other people's computers and I'm not sure I'm sold on that.
I've run into many situations where I'm remote and need to SSH into a NATed machine to fix something, and I typically will SSH reverse tunnel to a VPS.
From the NATed machine:
ssh -fN -R52222:localhost:22 user@publichost
ssh user@localhost -p 52222Shouldn't it be possible to use the central server only for hole-punching and implement a TCP-over-UDP connection so that the clients can directly communicate with each other? (And don't the major browser vendors already have public NAT-hole-punchers for WebRTC?)