SEO

#1 (**permalink**) 01-16-2008, 05:20 PM

I have two similarly configured workstations running HP-UX. One of them
works fine. The other does not. The symptom is that I cannot open 'dtterm'
using X forwarding. The messages are:

X11 connection uses different authentication protocol.
X11 connection rejected because of wrong authentication.

The strange thing is that it will forward xterm, xemacs, and even dtpad.
Why won't dtterm forward? I've run three different version of ssh (2.9,
3.5, and the latest) with the same results. I do not think it is ssh,
but perhaps someone can point me to the real problem.

Dimitri

#2 (**permalink**) 01-16-2008, 05:20 PM

On Mon, 03 Nov 2003 17:51:21 +0000, D. Gerasimatos wrote:

>
> I have two similarly configured workstations running HP-UX. One of them
> works fine. The other does not. The symptom is that I cannot open 'dtterm'
> using X forwarding. The messages are:
>
>
> X11 connection uses different authentication protocol. X11 connection
> rejected because of wrong authentication.

Perhaps you have disabled the MIT Magic-Cookie authentication or tried to
run dtterm as a user other than the one that established the SSH
connection?

Please provide more details explaining exactly what you are doing. dtterm
displays via SSH just fine. It would be more likely that xterm (R5 client)
would have problems, not dtterm.

#3 (**permalink**) 01-16-2008, 05:20 PM

"D. Gerasimatos" <dim@soda.csua.berkeley.edu> wrote in message
news:bo64ip$qt7$1@agate.berkeley.edu...
>
> I have two similarly configured workstations running HP-UX. One of them
> works fine. The other does not. The symptom is that I cannot open 'dtterm'
> using X forwarding. The messages are:
>
>
> X11 connection uses different authentication protocol.
> X11 connection rejected because of wrong authentication.
>
>
> The strange thing is that it will forward xterm, xemacs, and even dtpad.
> Why won't dtterm forward? I've run three different version of ssh (2.9,
> 3.5, and the latest) with the same results. I do not think it is ssh,
> but perhaps someone can point me to the real problem.

Can you try OpenSSH? And did you compile the ssh software locally on each
machine, or on a master machine that may have a different X configuration?
Do the machines have different default PATH's finding different versions of
xauth?

#4 (**permalink**) 01-16-2008, 05:23 PM

In article <XoudnRp--7wUFDWiRVn-sQ@comcast.com>,
Nico Kadel-Garcia <nkadel@comcast.net> wrote:
>
>Can you try OpenSSH? And did you compile the ssh software locally on each
>machine, or on a master machine that may have a different X configuration?
>Do the machines have different default PATH's finding different versions of
>xauth?

I was running OpenSSH. I did solve the problem. Someone changed ownership
of dtterm, which is a setuid exectuable. When I changed it back to root
all was well.

Dimitri

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode