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: OpenSSH vs. SSH.COM Key Management

Subject: Re: OpenSSH vs. SSH.COM Key Management
Date: Fri, 25 May 2007 11:34:41 +1000
Dan Reidy wrote:
I hope this is an appropriate question for this list.

I personally use OpenSSH as do most of the remote machines that I access. However, one administrator chooses to use the commercial version of SSH. I use Private/Public keys to logon to my remote machines. I am having a problem using my OpenSSH generated key to logon to the machine using the commercial version. They are apparently, non-compatible. Would any of you happen to have some advice on how to get this working correctly?

You can convert the OpenSSH generated key to the format expected by the version on the server. See OpenSSH's ssh-keygen(1):


 -e   This option will read a private or public OpenSSH key file and
      print the key in RFC 4716 SSH Public Key File Format to stdout.
      This option allows exporting keys for use by several commercial
      SSH implementations.

--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

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