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: ssh: problem with publickey authentication

Subject: Re: ssh: problem with publickey authentication
Date: Sun, 30 Oct 2005 21:16:39 +0200
On 10/30/05, Frans Englich <frans.englich@telia.com> wrote:

What have I screwed up this time? What does it mean by "Not a RSA1 key file"?
Should that file be an "RSA1" file, and what can I do to fix that? When I
created my key, I ran "ssh-keygen -t dsa". Whatever the fix, I would prefer
if it wouldn't require server changes.

I created a test user and ran "ssh-keygen -t dsa". It looked the same(except
for the data/numbers). I also tried connecting with that user, and it gave
the same errors("unknown key type" etc).

Any ideas what's wrong? I must say, ssh is *really* secure ;-)

How did you transfer the key to remote machine? I also use dsa key and
when running ssh with -vv get the same "unknown key type '-----BEGIN'"
errors but the key does work.

Try issuing next command to transfer the key to remote host:

cat ~/.ssh/id_dsa.pub | ssh user@remotehost "cat >> ~/.ssh/authorized_keys"

And then test the ssh connection again.

Regards,

--
[vl@dimir]#

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