On Saturday 29 October 2005 16:29, Vladimir Levijev wrote:
> On 10/29/05, Jeremy Eder <[EMAIL PROTECTED]> wrote:
> > also i believe the required modes for id_dsa and .pub is 600
>
> Not an issue, works with 600 as with 700.
Ok, this is getting a bit hilarious. I'm a simple Joe-user, not trying to harm
anyone, and I have these massive setup problems :)
I tried using 600 as per Jeremy's comment, but it didn't help. For the record:
bash-2.05b$ ls -alFh .ssh/
total 21K
drwx------ 2 frans users 160 Oct 30 17:22 ./
drwx------ 72 frans users 3.9K Oct 30 17:32 ../
-rw------- 1 frans users 736 Oct 30 17:22 id_dsa
-rw------- 1 frans users 604 Oct 23 18:53 id_dsa.pub
-rw------- 1 frans users 239 Oct 23 18:54 known_hosts
-rw------- 1 frans users 520 Oct 23 18:53 log.txt
I also tried increasing verbosity(-vvv, which I shamefully didn't know about),
and it showed some interesting output:
<SNIP>
debug1: Connection established.
debug1: identity file /home/frans/.ssh/identity type -1
debug1: identity file /home/frans/.ssh/id_rsa type -1
debug3: Not a RSA1 key file /home/frans/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /home/frans/.ssh/id_dsa type 2
<SNIP>
debug2: key: /home/frans/.ssh/identity ((nil))
debug2: key: /home/frans/.ssh/id_rsa ((nil))
debug2: key: /home/frans/.ssh/id_dsa (0x8093e90)
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/frans/.ssh/identity
debug3: no such identity: /home/frans/.ssh/identity
debug1: Trying private key: /home/frans/.ssh/id_rsa
debug3: no such identity: /home/frans/.ssh/id_rsa
debug1: Offering public key: /home/frans/.ssh/id_dsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).
So, is my private key broken on the syntax level? :) This is how it looks:
-----BEGIN DSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: <SNIP, a line of numerics/alpha>
<SNIP, roughly ten lines of what to me appears to be base64 encoded content>
-----END DSA PRIVATE KEY-----
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 ;-)
Cheers,
Frans
