Problem with ssh CVS access

[Ian Lance Taylor]

"Joel Sherrill <joel@OARcorp.com>" <joel.sherrill@OARcorp.com> writes:

> This all confuses me but I think I see what has happened.  The computer
> in our network DMZ that I always use to do cvs operations on secure
> repositories recently got an OS upgrade.
> 
> I hate to sound ignorant but does it sound like I lost the
> ssh key from my home directory in the upgrade?

It's possible, of course, although it's just in a file so I don't know
why it would have been lost unless you lost everything.  It should be
in the file ".ssh/identity".

> If so, is the solution that I will need to regenerate them with
> ssh-keygen?  What is the desired number of bits? And whom do I
> email it to?

Your log shows that you seem to have some keys, so you don't
necessarily need to regenerate any.  You can if you like, though.  I
don't think we care how many bits you use.  Just don't give away your
private key.  You can e-mail the public key (e.g., .ssh/id_dsa.pub) to
overseers.

> If I start over with a new key, then do I still have to force
> use of protocol 1?

Not if you generate a version 2 key, which I believe is the default
behaviour of ssh-keygen.

Ian