* Anibal Vasquez wrote on Sat, Oct 14, 2000 at 16:18 +0200:
Steffen Dettmer wrote:
ssh portforwaring before connecting. In that case you enable an ssh connection, forward the needed port(s) (i.e. 6000 IIRC), and connect to localhost. SSH forwards this connection encrypted to the other machine.
IFAIK, the X-server on machine B looks for an xdm by quering port 177 in the subnet where it is (if set up to query).
Well, I think if you specify the server at X start, no broadcasting is done, you shouldn't need to tunnel that.
B´s X-server´s port 6000 + Displaynumber. So it would be necessary to dinamically set up an SSH/SSL-tunnel from the port on machine A (choosen by the xdm running there) and port 6000 + Displaynumber on machine B.
Right, but in practise it should work if you forward 6000-6010 (i.e.) if you have less than 10 clients. I would just forward those ports and give a connect to localhost:1 (or whatever) a try. I think this could work, and so you won't have problems. If not, then it's time for searching the web a little ;)
Did I miss something? How can this be done? Where can I find info sources on this topic?
Well, I think you should use your favorite search engine to search for "xdm ssl stunnel ssh encryption" or something like that?! oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.