Thanx for the reply Scott,
Ive looked around on google.com, and I found some links that are based on
one of the bsd flavors.
Im really stuck when it comes to X, as I normally dont allow it to run on
our networks. The company I work for now cant live without it ( ug. users. )
so here I am.
I have even called Sun and the they simply refuse to support anything to do
with SSH, seeing as they dont have any secured shell natively. Sigh.
Another hint on this:
I know that xauth is being called. After the session connects and the error
comes through,
if you go over to /usr/dt/bin/ and type ./xauth you get the same problem. So
the problem is really not SSH itself. Im wondering now if its because of the
authentication spoofing?
The reason I wonder this, is because if your sitting in your $HOME dir and
type vi myfile
you get an error restricting your access to /temp.
In that case I turned off using "strict modes" in sshd_config. Even still it
didnt change the fact I was now being denied access to /temp. If I turn off
xforwarding in the client, slam.. no problems whatsoever.... the plot
thickens......
Robert
-----Original Message-----
From: Scott Armstrong [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 26, 2001 2:59 PM
To: Robert Buckley
Subject: Re: OpenSSH Solaris 8: timeout in locking authority file
/export/home/username/.Xauthority
Robert,
I haven't seen that problem with Solaris 8 SPARC or Solaris 8 x86 using
openssl-0.9.6/openssh-2.5.1p2 built with gcc 2.95.2
I haven't had a chance to update to later revisions. We're using automount
to float home directories.
Scott
----- Original Message -----
From: "Robert Buckley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 26, 2001 1:27 PM
Subject: OpenSSH Solaris 8: timeout in locking authority file
/export/home/username/.Xauthority
> Im wondering if anyone else out there has dealth with this problem?
>
> /usr/openwin/bin/xauth: tinout in locking authority file
> /exort/home/username/.Xauthority
>
> The ssh connection itself is fine. Its using the RSA auth method with the
> identity.pub file in the users $HOME/.ssh/authorized_keys.
> I thought that xdm is the providor for this type of session, but I dont
see
> anyplace where xdm calls xauth.
> Executing /usr/dt/bin/./dtterm at this point will give:
>
> debug1: Received X11 open request
> debug1: fd 7 setting O_NONBLOCK
> debug1: fd 7 US O_NONBLOCK
> debug1: channel 0: new [X11 connection from 192.168.0.23 port 32770]
> debug1: X11 connection uses different authentication protocol.
> debug1: X11 rejected 0 i1/o16
> ....
> ....
>
> So we at least know that OPENSSH is doing what its suppossed to do. I
> believe if I can solve the locking of the Xauthority file, I would be in
> business. Thank you in advance,
>
> Robert
>
>
>
