[rancid] ssh problems

['heasley']

Mon, May 15, 2017 at 07:49:52PM +0000, Wayne Eisenberg:
> Well, I did as you suggested and nothing changed. There are no problems contacting dozens of other devices with the exact same key. I'll let you know how it goes once that other device is updated.

it should no longer produce the same error though; correct?

> -----Original Message-----
> From: 'heasley' [mailto:heas at shrubbery.net] 
> Sent: Friday, May 12, 2017 11:43 AM
> To: Wayne Eisenberg
> Cc: 'heasley'; 'Scott Granados'; 'rancid-discuss at shrubbery.net'
> Subject: Re: [rancid] ssh problems
> 
> Fri, May 12, 2017 at 03:33:27PM +0000, Wayne Eisenberg:
> > I was just informed that there is some kind of network device sitting in front of the firewall, intercepting traffic. I will get that resolved first and then try rancid again, so this troubleshooting is temporarily on hold. Thanks for the suggestions, though.
> 
> that is not the problem.  that error is clearly from the client program,
> ie: local.
> 
> > 
> > -----Original Message-----
> > From: heasley [mailto:heas at shrubbery.net]
> > Sent: Thursday, May 11, 2017 10:44 AM
> > To: Wayne Eisenberg
> > Cc: 'Scott Granados'; 'rancid-discuss at shrubbery.net'
> > Subject: Re: [rancid] ssh problems
> > 
> > Thu, May 11, 2017 at 04:41:38AM +0000, Wayne Eisenberg:
> > > The ASA? The key there existed before my involvement, so I have no idea where it was generated. But I thought this was a problem with the local key of the rancid host, which was generated on it.
> > 
> > well, it seems to be in the wrong format; given the error, probably PKCS.
> > 
> > > debug3: Not a RSA1 key file /home/rancid/.ssh/id_rsa.
> > > debug2: key_type_from_name: unknown key type '-----BEGIN'
> > 
> > move it aside, and
> > 
> >         % ssh-keygen -t rsa
> > 
> > ________________________________
> > 
> > The information in this Internet e-mail (and any attachments) is confidential, may be legally privileged and is intended solely for the Addressee(s) named above. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, then any dissemination or copying of this e-mail (and any attachments) is prohibited and may be unlawful. If you received this e-mail in error, please immediately notify us by e-mail or telephone, then delete the message. Thank you.