On Sat, 28 Aug 1999, Michael wrote:
> Don't know anything about LBX, but can't you start an ssh session
> as a regular session i.e. ssh -x, port forward the connection you
> need and open your LBX session over the forwarded port??
> You should be able to script the whole thing.
> [EMAIL PROTECTED]
You may be right, but unfortunately I don't know enough about the X
connections to do so. I can only tell you something about LBX, so that you
may be able to provide me with some more detailed guidance...
After starting a regular session (ssh -x or even telnet etc.) from LOCAL
(my screen and X-server is here) to REMOTE (my application runs here) I
can say:
xauth add LOCAL:0 . <MIT-MAGIC-COOKIE obtained by `xauth list' on LOCAL>
lbxproxy -display LOCAL:0 (xauth is needed for this)
xauth add :63 . <the same COOKIE> (:63 is the default for lbxproxy)
export DISPLAY=:63 (further connections through lbxproxy)
xclock, etc.
This way the the connections get compressed and protected by a COOKIE, but
not encrypted. If I do plain `ssh' (with X forwarding enabled), then
`lbxproxy' runs (without any parameters, of course), but connections
through it are refused even if I copy ssh's fake COOKIE of $DISPLAY into
that of :63.
Concerning your suggestion above: as far as I know, X connections come to
the local port 6000, so I should forward that, but to which remote port? I
have got no control over the port number chosen on the other side, or have
I? Or am I speaking nonsense?
Feri
