Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pipe keys to pbcopy instead of opening them in an editor #1

Open
drinks opened this issue Mar 16, 2012 · 4 comments
Open

Pipe keys to pbcopy instead of opening them in an editor #1

drinks opened this issue Mar 16, 2012 · 4 comments

Comments

@drinks
Copy link

drinks commented Mar 16, 2012

Under the section 'Continue setting up git' in the readme, a process for opening the public key in a text editor is described. It's way easier to cat the key and pipe to the mac os app pbcopy to put it in your clipboard.

cat ~/.ssh/id_rsa.pub | pbcopy
@desandro
Copy link
Contributor

The training session was eye opening. It was catered towards those with no experience with Git or the command line. While that script is useful, I am thinking it might be better just to eliminate anything to do with the Terminal. Have all the SSH keys stuff taken care of with one AppleScript or something that people can just double click to set up. Enter in email, then passphrase, boom, it's done.

@drinks
Copy link
Author

drinks commented Mar 16, 2012

I haven't tried to reproduce it, but I think the github app might have generated and uploaded keys for somebody I was working with recently when they logged in; it would be pretty great if that turns out to be the case.

@desandro
Copy link
Contributor

I do know that GitHub app did automatically read the SSH keys and associate them with their account on github.com

@drinks
Copy link
Author

drinks commented Mar 16, 2012

Fancy.

Dan Drinkard

On Friday, March 16, 2012 at 4:44 PM, David DeSandro wrote:

I do know that GitHub app did automatically read the SSH keys and associate them with their account on github.com (http://github.com)


Reply to this email directly or view it on GitHub:
#1 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants