Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: Using public key pair to authenticate

Subject: Re: Using public key pair to authenticate
Date: Wed, 24 Nov 2004 08:03:21 -0500
On Tue, Nov 23, 2004 at 04:57:33PM -0700, Loo, Peter wrote:
I am working with two Unix servers running AIX 5.2.  One server is
running "OpenSSH_3.6.1p2-CERT-patched, SSH protocols 1.5/2.0, OpenSSL
0x009060df" while the other is running "SSH Secure Shell 3.2.0".

I created the key pair on the server with OpenSSH using "ssh-keygen".
[...]

OpenSSH and SSH.Com have different key file formats.  You must use
ssh-keygen to convert from one to the other.

If you use OpenSSH's ssh-keygen(1) to do the conversion, you probably
want to use the -e option.  I have no idea what the corresponding option
is for SSH.Com's implementation.

named the output files as (identity & identity.pub).  Then I copied the
contents of "identity.pub" to the file named authorized_keys on the
server with "SSH Secure Shell 3.2.0".  

Sounds like you built an rsa1 type keypair.  That's not going to work
very well with an SSH2 server.  Try this instead:  ssh-keygen -t rsa

(No, I have no idea why OpenSSH is defaulting to type rsa1.)

<Prev in Thread] Current Thread [Next in Thread>