On Thu, Mar 15, 2007 at 02:46:06PM +0100, Jim van Wel wrote:
> > On Thu, Mar 15, 2007 at 02:03:45PM +0100, Jim van Wel wrote:
> >> > On Thu, Mar 15, 2007 at 11:42:44AM +0000, Eur Ing Chris Green wrote:
> >> >> On Thu, Mar 15, 2007 at 12:35:52PM +0100, Jim van Wel wrote:
> >> >> > Hi there,
> >> >> >
> >> >> > > debug3: Not a RSA1 key file /home/chris/.ssh/id_rsa.
> >> >> > > debug2: key_type_from_name: unknown key type '-----BEGIN'
> >> >> >
> >> >> > Your rsa_key is not alright? Are you working with SSH keys?
> >> >> >
> >> >> I was wondering what that was about too. The odd thing is that it
> >> >> appears to work, if I remove my /home/chris/.ssh/id_rsa file (well,
> >> >> rename it) then when I use ssh the remote hosts ask for my password.
> >> >>
> >> >> Maybe I'll try regenerating all my keys, those ones are quite old.
> >> >>
> >> > It makes no difference, I still get all that stuff (in debug) about
> >> > "Not a RSA1 key file /home/chris/.ssh/id_rsa", all my ssh logins do
> >> > the same but they all work OK except one.
> >> >
> >> Can you post your sshd_config here? Maybe some strange line somewhere.
> >> How
> >> did you generated the keys? Looks like the SSH-RSA is not working right.
> >> It needs to parse your public key, and it is not doing this at this
> >> moment.
> >>
> > I generated my keys by saying "ssh_keygen" and accepted the default
> > file name.
> >
> When you look at your id_rsa files, does it looks like it's starting with
> this:
>
> -----BEGIN RSA PRIVATE KEY-----
> Proc-Type: 4,ENCRYPTED
>
> many code
>
> -----END RSA PRIVATE KEY-----
>
Yes, exactly as you describe.
> and id_rsa.pub:
>
> ssh-rsa MANY CODE
> me@xxxxxxxxxxxxxxxxxxxxx
>
Yes again, it looks exactly like this.
>
> Normally when I generate via ssh-keygen I do this:
>
> ssh-keygen -t rsa -b 2048
>
> So you now for sure you are using RSA instead of DSA.
> Also knowing you use rsa instead of rsa1 for example.
>
The man page for the ssh-keygen command here says:-
If invoked without any arguments, ssh-keygen will generate an
RSA key for use in SSH protocol 2 connections.
So I took it at its word! :-)
--
Chris Green
