Why is %#$& X11 failing to authorize this SSH connection? :(

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: R P Herrold
Date:  
To: Main PLUG discussion list
Subject: Why is %#$& X11 failing to authorize this SSH connection? :(
On Mon, 26 Jul 2010, wrote:

> So I do:


> kitepilot@beechjet:~$ ssh -vvv -fCX ayx09@turbocommander VirtualBox >
> /tmp/junkX11-VirtualBox.log 2>&1
> And I get my Virtual Box screen up and I can do whatever I want except to
> star a VM because:


> When I do this:
> kitepilot@beechjet:~$ ssh -vvv -fCX ayx09@turbocommander 'VBoxManage startvm
> Unum' > /tmp/junkX11-VBoxManage.log 2>&1
> X11 fails to authorize!


You flopped the URLs and the session logs relative toyour
narrative so I identify them

the first http://www.kitepilot.com/junkX11-VBoxManage.log

debug1: client_input_channel_open: ctype x11 rchan 3 win 65536
max 16384
debug1: client_request_x11: request from 127.0.0.1 33887
debug2: fd 4 setting O_NONBLOCK
debug3: fd 4 is O_NONBLOCK
debug1: channel 1: new [x11]
debug1: confirm x11
debug3: Wrote 48 bytes for a total of 3015
debug2: X11 connection uses different authentication protocol.
X11 connection rejected because of wrong authentication.
debug2: X11 rejected 1 i0/o0



the second    http://www.kitepilot.com/junkX11-VirtualBox.log


debug1: client_input_channel_open: ctype x11 rchan 3 win 65536
max 16384
debug1: client_request_x11: request from 127.0.0.1 33888
debug2: fd 4 setting O_NONBLOCK
debug3: fd 4 is O_NONBLOCK
debug1: channel 1: new [x11]
debug1: confirm x11
debug3: Wrote 48 bytes for a total of 2999
debug3: Wrote 464 bytes for a total of 3463

The MIT magic cookie exchange, needed for xauth and
credentials forwarding is failing on the first

The command being passed in is:

     debug1: Sending command: VBoxManage startvm Unum


Something like this may work from the client side

     su - -c VBoxManage startvm Unum


per: info su:

...
      login startup file(s).  Additionaly `DISPLAY' and `XAUTHORITY'
      environment variables are preserved as well for PAM functionality



Run the first inside a terminal login subshell, and it should
succeed The management interface probably does not spawn a
pty by default and it is needed for the authentication
exchange

-- Russ herrold
---------------------------------------------------
PLUG-discuss mailing list -
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss