From: Kontizas Demostenis (kdemostenis@gmail.com)
Date: Tue Oct 31 2006 - 13:00:21 EST
Issue resolved. Thanks to Andew Mehlos.
Thanks for the great troubleshooting tips.
The dump on the daemon side showed the following:
Authentication refused: bad ownership or modes for directory
/export//home/user/JaneDoe
On 10/31/06, Andrew Mehlos <Andrew.Mehlos@ge.com> wrote:
> On Tue, 2006-10-31 at 10:58 -0500, Kontizas Demostenis wrote:
> > debug2: read_server_config: filename /usr/local/etc/sshd_config
> > debug1: sshd version OpenSSH_3.8.1p1
> > debug1: private host key: #0 type 0 RSA1
> > debug3: Not a RSA1 key file /usr/local/etc/ssh_host_rsa_key.
> > debug1: read PEM private key done: type RSA
> > debug1: private host key: #1 type 1 RSA
> > debug3: Not a RSA1 key file /usr/local/etc/ssh_host_dsa_key.
> > debug1: read PEM private key done: type DSA
> > debug1: private host key: #2 type 2 DSA
> > debug1: Bind to port 22222 on ::.
> > Server listening on :: port 22222.
> > debug1: Bind to port 22222 on 0.0.0.0.
> > Server listening on 0.0.0.0 port 22222.
> > Generating 768 bit RSA key.
> > RSA key generation complete.
> >
> That all looks pretty reasonable -- what you need
> to look at is the debugging info that the sshd process will
> output when the other host tries to connect to it after
> the "ssh -p 22222 host1".
>
>
>
> > On 10/31/06, Andrew Mehlos <Andrew.Mehlos@ge.com> wrote:
> > > On Tue, 2006-10-31 at 10:33 -0500, Kontizas Demostenis wrote:
> > > > Ladies and Gentlemen I have two machines which I am trying to create
> > > > passwordless ssh sessions between them but it will not work, these
> > > > same boxes work with passwordless ssh to linux boxes but not to
> > > > eachother. What could be the problem? Can someone please explain a
> > > > fix to this issue? Thanks.
> > >
> > > You can probably diagnose this better by running the ssh daemon in the
> > > foreground with debugging turned up - On host #1 do:
> > >
> > > root@host1# /opt/openssh/sbin/sshd -ddd -p 22222
> > >
> > > This starts sshd with all the debugging info turned on.
> > >
> > > On host #2, try and connect to it on the port specified above (22222)
> > >
> > > user@host2$ ssh -p 22222 host1
> > >
> > >
> > >
> > > ..And see what comes out of the debugging info on both sides.
> > >
> > > All that being said, I think about 3 out of 4 ssh problems I run into
> > > are because some user changed the permissions on their home directory or
> > > in $HOME/.ssh to make them world or group writable, which will cause ssh
> > > to not trust them.
> > >
> > >
> > > HTH.
> > >
> > > --asm
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:41:07 EDT