Re: X11 forwarding in OpenSSH question

From: NetNews (narbuzov_at_att.com)
Date: 11/17/03 

Date: Mon, 17 Nov 2003 09:36:13 -0500

I don't neet to set DISPLAY variable to hostA:0.0. This way X11
traffic will never go through SSH connection.
If you have X11 forwarding enabled DISPLAY should be st to
localhost:11.0 or something like that. It depends which port
SSH will open for X11 redirection. Check netstat -an | grep for 60

tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6011 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6012 0.0.0.0:* LISTEN

"Mike" <mikeumo@onebox.com> wrote in message
news:5B_tb.1187$AT2.991@newssvr22.news.prodigy.com...
> Hello,
>
> I wonder if someone could help me with this problem.
>
> I have two Linux boxes on LAN (both Mandrake 9.1 on i586, static IP), say
> BoxA and BoxB. BoxA runs X server and BoxB runs sshd
> (openssh-3.6.1p2-mdk1.2.91). I use ssh client (openssh-3.6.1p2-mdk1.2.91)
> from BoxA to login as a user to BoxB where I run X Windows programs (say,
> konqueror) which I want to display on BoxA. As is, situation results in
> (case 1):
>
> libGL error: failed to open DRM: Operation not permitted
> libGL error: reverting to (slow) indirect rendering
> kbuildsycoca running...
> libGL error: failed to open DRM: Operation not permitted
> libGL error: reverting to (slow) indirect rendering
> mcop warning: user defined signal handler found for SIG_PIPE, overriding
> ... # and many more as I navigate in the opened browser
>
> and konqueror does start, but, as it says, in a slow mode.
>
>
> if I set the DISPLAY variable (in /etc/profile like DISPLAY=BoxA:0.0;
> export DISPLAY) on BoxB to point to BoxA's display then I get (case 2):
>
> Xlib: connection to "192.168.1.3:0.0" refused by server
> Xlib: No protocol specified
> konqueror: cannot connect to X server 192.168.1.3:0.0 # i.e. BoxA display
>
> now if I use xhost on BoxA to add BoxB to BoxA's access control list
(xhost
> +BoxB) then I get only (case 3):
>
> kbuildsycoca running...
> mcop warning: user defined signal handler found for SIG_PIPE, overriding
>
> so, there seem to be fewer problems now. Now the question:
>
> why ssh/sshd do not resolve connections in the first case automatically?
>
> I have X11 forwarding enabled in both ssh-client and sshd. It looks to me
> that md5sum cookies do not work in the first ssh case. I also tried to
> extract/merge .XAuthority from BoxA to BoxB with no changes in output.
>
> Can someone help me to understand the process of ssh forwarding and X
server
> authentication. The man and HOW-TO pages on this matter are confusing.
>
> Thank you in advance,
> Mikhail.
>
>
>

Relevant Pages

  • Re: X11 forwarding in OpenSSH question
    ... This will forward all X-display stuff through the SSH tunnel, ... BoxA runs X server and BoxB runs sshd ... $>whoami: Carl Holtje $>mail holtje: cwh0803@cs.rit.edu ...
    (comp.security.ssh)
  • Re: piggy-backing through an ssh session
    ... When you ssh from box A to box B you can port forward port 1234 on box B ... example hacked from my .ssh/config file at home (boxa) is: ... This method only allows boxb to ssh to boxa. ...
    (comp.security.ssh)
  • X11 forwarding in OpenSSH question
    ... BoxA and BoxB. ... BoxA runs X server and BoxB runs sshd ... libGL error: failed to open DRM: Operation not permitted ...
    (comp.security.ssh)
  • Re: Checking if textbox values have been cleared or replaced, or updated
    ... > with new ones before updating the record. ... BoxA would be visible and that's where the users would ... BoxB would be invisible and for checking purposes only. ... both boxes are not null. ...
    (microsoft.public.access.queries)
  • RE: missing vim highlight
    ... Using vim, on boxA, if for example, I use the slash ... On boxB, there is no highlight ...
    (Fedora)