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. |

| Subject: | RE: Using public key pair to authenticate |
|---|---|
| Date: | Wed, 24 Nov 2004 11:45:49 -0500 (EST) |
Part of it has to do with the way that OpenSSH and SSH.com internally handle their keys. The default for OpenSSH is that the key is stored in authorized_keys in the .ssh directory with the following format: ssh-dss bunch_of_base64_encoded_key_junk user@example.com while ssh.com has a file in the .ssh2 directory called authorization that contains the following type of info: key PublicKey.pub where PublicKey.pub will be in the .ssh2 directory in the following format: ---- BEGIN SSH2 PUBLIC KEY ---- Subject: your_subject Comment: "1024-bit dsa, user@example.com, Thu Dec 06 2001 14:22:13" bunch_of_base64_encoded_key_junk_with_line_breaks_at_every_seventy_fir st_column ---- END SSH2 PUBLIC KEY ---- If you change the formatting around to correspond with these, that should work. At least, that's what I did, and it seemed to work for me. --Matthew Dalton On Wed, 24 Nov 2004, Tay, Gary wrote:
You may search SUN's BigAdmin portal or Google for "authorized_keys". Some good ones: http://www.sun.com/bigadmin/features/articles/sec_shell_1.html http://www.sun.com/bigadmin/features/articles/sec_shell_2.html Most people would start SSH server in debug mode, "sshd -d", and also test ssh client connection using vervose mode, "ssh -v remotehost" Gary -----Original Message----- From: Loo, Peter [mailto:Peter.Loo@bannerhealth.com] Sent: Wednesday, November 24, 2004 7:58 AM To: secureshell@securityfocus.com Subject: Using public key pair to authenticate Hi, 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". I 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". When I try connecting to the remote server, I am asked to type in the password. Apparently the public key authentication method is not working. Can someone shed some light for me? Thanks. Peter
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Using public key pair to authenticate, Alexander Klimov |
|---|---|
| Next by Date: | Re: Using public key pair to authenticate, Greg Wooledge |
| Previous by Thread: | RE: Using public key pair to authenticate, Tay, Gary |
| Next by Thread: | RE: Using public key pair to authenticate, Tay, Gary |
| Indexes: | [Date] [Thread] [Top] [All Lists] |