Andrew Falanga writes: >> >> >debug1: Authentications that can continue: publickey,keyboard-interactive >> >debug1: Next authentication method: publickey >> >debug1: Trying private key: /home/andy/.ssh/identity >> >debug1: Offering public key: /home/andy/.ssh/id_rsa >> >debug2: we sent a publickey packet, wait for reply >> >debug1: Authentications that can continue: publickey,keyboard-interactive >> >> It seems OpenSSH (on your dad's box) hasn't recognized your private key, so >> how about checking permissions of ~/.ssh/authorized_keys and ~/.ssh on his >> box. Or how about enabling verbose logging on his box, using 'LogLevel' >> parameter in sshd_config. >> >> HTH >> Ashish Shukla
> Following onto the e-mail I made before, apparently that little permissions > difference for the directory, .ssh, was the problem. Changing it to 644 has, > apparently, fixed the problem. Cool :) . I learnt this from my first SSH public-key authentication configuration ;) Ashish -- () ascii ribbon campaign - against HTML e-mail /\ www.asciiribbon.org - against proprietary attachments ·-- ·- ···· ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- % dig +short cname cdac.in @::1 ms.gov.in
pgp4Immu00LG0.pgp
Description: PGP signature
