Re: [tlug] Securing X-Window Protocol

["Stephen J. Turnbull" <stephen@example.com>]

>>>>> "Jim" == Jim  <jep200404@example.com> writes:

    Jim> This capability is native to ssh and can be enabled or
    Jim> disabled in its configuration. I usually don't bother for
    Jim> xterm, but it's very handy for things like browsers and
    Jim> k3b. I haven't tried using it for a window or desktop
    Jim> manager.

As far as X clients (including window and desktop managers, which are
just clients with special features) are concerned, it's just a local X
server listening on (usually) port 6010.  The only thing special ssh
does (vis-a-vis ordinary port forwarding) when X forwarding is enabled
is to export "DISPLAY=:10.0" in the environment of the remote shell.

As far as the X server is concerned, port-forwarded clients are just
ordinary clients calling on (usually) port 6000.

It's really that simple, so I'd be very surprised at anything that
didn't work.

Sometimes I'm just so overwhelmed by the elegance of it all, I get all
choked up. :-)

-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.