On May 24, 10:50 am, Lee Hambley <[email protected]> wrote:
> > 20 pages of documentation for a key - are you kidding?
>
> No.
>
> Keys are valuable - probably more valuable than the keys you have in real
> life depending what project you are working on - the better you understand
> that, and how keys work - the better you will be at your job.
>


Huh. I've never used ssh keys on a job.

I'm probably going to need this information maybe once every two years
and at that rate I'm worried that I'll lose my understanding. I can't
remember which tutorial got me the result I wanted last time, so I
can't easily compare it to anything.

Is the documentation covering Windows? It doesn't seem to be. Quote:

   While I try to keep the HOWTO as generic and inter-operable as
possible,
   it could happen that I write an example that is not working on your
*NIX,
   please let me know.

I'm not confident in my ability to learn *NIX concepts and then relate
those to how I use Windows. I've never been good at using unix.

I have a Github account and Git on my machine that I installed using
msysgit. I don't have the context menus "Git Gui Here" or "Git Bash
Here" -- for some reason msysgit installer never prompted me for
those. I searched around and noticed that another had that problem.
This may be totally irrelevant -- or not.  
http://code.google.com/p/msysgit/issues/detail?id=231

I'm trying to recall how I got it running last time and I think it was
a page on Github website that explained keys for Windows.

> Short answer: Generate and distribute a new one.
>

Got it. I have puttygen and pageant. I think there was a tutorial on
Github for how to tell git what the key is and tell github what the
key (or keys?) are.

Thanks for the help -- I'm trying not to whine -- I just don't
understand this stuff well.

-- 
You received this message because you are subscribed to the Google Groups 
"GitHub" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/github?hl=en.

Reply via email to