On Mon, Nov 15, 2010 at 13:45, Paul Heinlein wrote:
> On Mon, 15 Nov 2010, cliff here wrote:
>
> > You should check the perms on the dirs, ssh will not allow it use
> > the keys if they are too permissive. So I would check starting at
> > /home
>
> This is the most likely cause; I'd check there t
I do believe the perms need to be at 700 for the ./ssh dir and 640 for the
actual key files contained.
On Mon, Nov 15, 2010 at 1:45 PM, Paul Heinlein wrote:
> On Mon, 15 Nov 2010, cliff here wrote:
>
> > You should check the perms on the dirs, ssh will not allow it use
> > the keys if they are t
On Mon, 15 Nov 2010, cliff here wrote:
> You should check the perms on the dirs, ssh will not allow it use
> the keys if they are too permissive. So I would check starting at
> /home
This is the most likely cause; I'd check there too.
If not,
1. Ensure the file hash is the same (e.g., no ex
You should check the perms on the dirs, ssh will not allow it use the keys
if they are too permissive. So I would check starting at /home
On Mon, Nov 15, 2010 at 1:29 PM, John Kennedy wrote:
> All,
> I have 3 servers. All 3 are CentOS 5.5. All 3 have identical
> /etc/ssh/sshd_config files. I use
All,
I have 3 servers. All 3 are CentOS 5.5. All 3 have identical
/etc/ssh/sshd_config files. I used ssh-keygen (with no arguments) to
generate keys with no password. I then added all 3 id_rsa.pub keys to the
authorized_keys file.
With this set up, I should be able to ssh between all 3 boxes withou
5 matches
Mail list logo