The answer is in the debug output you provided.  Notice that authorized_keys has 
group write access.  Do a chmod 600 ~/.ssh/authorized_keys.  This should solve 
your problem.  

BTW, I would recommend going to a version 2 protocol private/public 
authentication.  For that, you would want to use ssh-keygen -t rsa|dsa to 
generate one of them.  The publec side then goes in ~/.ssh/authorized_keys2.

Hope this helps.

        -Dave
        

>debug1: Remote: RSA authentication refused for user:
>bad ownership or modes for
>'/home/user/.ssh/authorized_keys'.
>debug1: Server refused our key.
>debug1: Doing password authentication.
>
>$ls -ld .ssh
>drwxrwxr-x 2 user grp    512 Jul 29 14:02 .ssh
>
>$> cd .ssh
>$> ls -l
>-rw-rw-r-- 1 user grp  339 Jul 29 14:02
>authorized_keys
>-rw-r--r-- 1 user grp  339 Jul 29 14:02 identity.pub
>-rw------- 1 user grp 1024 Jul 23 10:28 prng_seed
>$> 
>


--
David Knight French                           
Black Mountain Computer Consulting
Voice: (858)573-2959
Email: [EMAIL PROTECTED]

Reply via email to