On Mon, Nov 03, 2008 at 07:29:46PM -0700, Andrew Falanga wrote: > > > > > >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.
Which doesn't make sense for two reasons: 1) Directories must have the execute bit set (644 lacks that), 2) ~/.ssh should be 700 for security reasons. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
