RE: Publick key authentication problem
- From: "Pfister, Thomas P" <pfister@xxxxxxxxxxx>
- Date: Fri, 26 May 2006 16:19:21 -0400
My experience with OpenSSH is limited to getting OpenSSH clients to work
with our commercial SSH server, so more experienced OpenSSH admins can
confirm or correct my thoughts here.
These lines from your attachment, ssh.log, look to me like your key file
has been converted to be compatible with ssh.com's commercial product:
debug2: key_type_from_name: unknown key type '-----BEGIN'
....
debug2: key_type_from_name: unknown key type '-----END'
But I believe you said that these same keys work on a different SSH
Server. Might that server be running the commercial SSH server from
ssh.com instead of OpenSSH? That would explain this key file working
there but not on this server.
You also do not have an identity file in your .ssh directory. This file
should have an entry that looks like "IDKey id_dsa". I can't explain
why your connection works to any server without this file.
Tom Pfister
UITS - Enterprise System Administration
-----Original Message-----
From: Frans Englich [mailto:frans.englich@xxxxxxxxx]
Sent: Friday, May 26, 2006 6:22 AM
To: secureshell@xxxxxxxxxxxxxxxxx
Subject: Publick key authentication problem
Hi everyone,
I have trouble connection to a server with ssh. I've tried solving this
before, but failed. I won't stop this time until this works.
These are the commands I execute:
--------------------------------
bash-2.05b$ exec ssh-agent bash
bash-2.05b$ export CVS_RSH=`which ssh`
bash-2.05b$ ssh-add
Enter passphrase for /home/frans/.ssh/id_dsa:
Identity added: /home/frans/.ssh/id_dsa (/home/frans/.ssh/id_dsa)
--------------------------------
Running `ssh-add -l' in the current shell gives:
--------------------------------
2048 2e:f5:49:d6:21:a0:50:83:1e:a4:fd:90:66:5a:f5:76
/home/frans/.ssh/id_dsa
(DSA)
--------------------------------
Now, running `ssh -vvv englich@HOSTNAME 2> ssh.log' gives "Permission
denied
(publickey)." The full output is attached, ssh.log.
This is how my .ssh/ directory looks:
--------------------------------
bash-2.05b$ ls -alFh .ssh/
total 30K
drwx------ 2 frans users 136 May 17 19:38 ./
drwx------ 81 frans users 5.0K May 26 10:00 ../
-rw------- 1 frans users 1.3K May 17 18:28 id_dsa
-rw-r--r-- 1 frans users 1.1K May 17 18:28 id_dsa.pub
-rw-r--r-- 1 frans users 15K May 26 09:49 known_hosts
--------------------------------
Before identifying any problems, you should know that I manage to
*commit*
with CVS over ssh to another server, so something with my ssh setup
seems to
be right.
In my .ssh/known_hosts file, the server I'm having trouble connecting to
has
"ssh-rsa", while my files are "DSA" -- could this have to do with it?
However, the server I can connect to is also "ssh-rsa", so that seems to
rule
it out.
What is wrong?
One might argue that my public key is corrupt on the server side, but I
sent
it as an email attachment(with the same MUA) in the same way to the
admins of
both servers.
I would really appreciate help on this, I've run out of ideas. Let me
know if
I can supply anymore info.
Cheers,
Frans
- Follow-Ups:
- Re: Publick key authentication problem
- From: Frans Englich
- Re: Publick key authentication problem
- Prev by Date: Re: Publick key authentication problem
- Next by Date: Re: Publick key authentication problem
- Previous by thread: Re: Publick key authentication problem
- Next by thread: Re: Publick key authentication problem
- Index(es):
Relevant Pages
|
|
