And mysteriously, after two reboots... it works. Don't know why, but it does. RF Robert G. Freeman Oracle Consultant/DBA/Author Principle Engineer/Team Manager The Church of Jesus Christ of Latter-Day Saints Father of Five, Husband of One, Author of various geeky computer titles from Osborne/McGraw Hill (Oracle Press) -----Original Message----- From: Greg Norris [mailto:spikey.mcmarbles@xxxxxxxxx] Sent: Tuesday, May 01, 2007 7:05 PM To: robertgfreeman@xxxxxxxxx Cc: oracle_L_list Subject: Re: SSH Autologin problem On 5/1/07, Greg Norris <spikey.mcmarbles@xxxxxxxxx> wrote: On 5/1/07, Robert Freeman <robertgfreeman@xxxxxxxxx> wrote: If you haven't already, doublecheck the permissions on ~/oracle/.ssh, ~oracle, and all of the parent directories. OpenSSH, which is what I assume you're using, can be quite picky about group/world-writeable directores... it's possible to disable this check by setting "StrictModes no" in sshd_config, although that wouldn't be my recommended approach. Another possibility (albeit unlikely) would be that the sysadmin has explicitly disabled public-key authentication, either globally or for specific users/groups. An examination of sshd_config should reveal this, assuming that they haven't also made the file unreadable (as my own sysadmins are rather fond of doing). It might also be helpful to run the ssh client in verbose mode, like: $ ssh -v node1 or $ ssh -vvv node1 -- "I'm too sexy for my code." - Awk Sed Fred.