Neat. I use the following incantation when authorizing folks to ssh into my servers via github public keys: curl https://github.com/[github name].keys >> ~/.ssh/authorized_keys [github name] here should be replaced with github username of your friend or colleague. Really handy because I can just authorize them without a human request/response loop and manual key moving. Simple and no external tools needed. Normal cav…
Show HN: Invite friends to SSH into your laptop using their GitHub handle
61–70 of 105 posts
Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#62Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#63Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#64Regarding remote pair programming I haven't found a better or faster solution than TMate ( https://tmate.io/ ) If I am feeling paranoid about the user on the other side, I only share just the read-only link, or the web link.
Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#65Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#66Earlier quoted context omitted.
would be nice, but it would likely introduce some additional complexity for instances where there might be more than one live session spawned by a user.
> additional complexity for instances where there might be more than one live session spawned by a user I'm trying to imagine the situation that makes that worth supporting? That's not going to be a development server used by an entire team, for example, because whose Github credentials would be on it? Even so, it could just give a list of session IDs in such a case, and ask which of 1/2/3. The additional complexity…
Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#67Neat. I use the following incantation when authorizing folks to ssh into my servers via github public keys: curl https://github.com/[github name].keys >> ~/.ssh/authorized_keys [github name] here should be replaced with github username of your friend or colleague. Really handy because I can just authorize them without a human request/response loop and manual key moving. Simple and no external tools needed. Normal cav…
The beauty of doing it this way (writing authorized_keys) is that the accounts are completely independent from a third-party auth service. (ok, I guess technically that's what we are, but we're only managing the public keys, and not directly authenticating through a remote server like a directory or database.) SSH has a beautiful design.
Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#68Earlier quoted context omitted.
> additional complexity for instances where there might be more than one live session spawned by a user I'm trying to imagine the situation that makes that worth supporting? That's not going to be a development server used by an entire team, for example, because whose Github credentials would be on it? Even so, it could just give a list of session IDs in such a case, and ask which of 1/2/3. The additional complexity…
In my head, having to have the session id is almost a good "two factor" if you will.
Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#69I prefer using tmux for this to be a bit more secure. I wrote a blog post about this [0] since it is a bit of a pain in the ass to set up properly. Maybe you should explore this too for your product. [0] http://joy.pm/2015/07/11/pairing_over_tmux.html
Re: Show HN: Invite friends to SSH into your laptop using their GitHub handle
#70Hey HN - This is basically a hosted version of Teleport[0], which may scare some people. We don't store the sessions and you can always self-host if you prefer. [0] http://gravitational.com/teleport/
This looks pretty useful for highly dynamic infrastructure. How can nodes register with the Teleport service on provision? Do you integrate with third party authentication services like HashiCorp Vault?
Vault is not yet supported but PR's welcome :)
edit: Looks like there's an open issue for consul to start: https://github.com/gravitational/teleport/issues/423