Re: [foxboro] ssh problems after upgrade

On Wed, Aug 27, 2003 at 07:54:54PM -0500, Corey R Clingo wrote:
> 
> Well, for one, you need to copy the *pub file to ~/.ssh/authorized_keys (or
> maybe authorized_keys2 for an ssh as old as the one you are using), not
> known_hosts.  The known_hosts file on the machine you are ssh-ing _to_ has
> no effect.
> 
> Also, check permissions on your local key files; they have to be 600 I
> believe.
> 

Thnaks.

Turned out the / (which is root's home directory) had it's group wrtie bit
set. ssh is _very_ picky about directory permissions. BTW, I found this by
running the sshd (daemon) in debug mode, and watching the output. 

Part of what was confusing me was, I had this problem before, and I thought
the running ssh with the -v option would give me a message about this, but
it did not.

-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
                                                -- Benjamin Franklin
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: