Tru64 Installation on FreeAXP

Your X-11 server on the PC must be able to listen to connections on 127.0.0.1:6000 for server 0, screen 0. That should be the default for most X11 servers.

From Putty (not the opa0 console connection), Under SSH, Under X11, you need to have X11 enabled X11 forwarding. X-display location should be localhost:0.0 (Or matching the server / screen above)

Then you can enable MIT-Magic-Cookie-1.

When you SSH to the hostname of the target system, the SSH session should have a 'DISPLAY" environment variable preset for the private server for your session.

$ echo $DISPLAY
localhost:10.0

Note that the number after localhost will vary because it will be unique to that node.

So from that point on, just running an X-11 application on that SSH connection should just work.

On VMS, the command SHOW DISPLAY will show the connection. There is a bug in all known VMS implmentations in that the host should be localhost, and is instead showing the public hostname. If the VMS host is behing a NAT connection, you have to recreate the display connection with hostmame localhost for it to work.

Maybe I missed something ... but a 'basic' PC X11 Server doesn't need any form of 'secure' connection. Provided your client PC with its Xserver can 'see' the Tru64 instance, xdmcp will get/find the CDE/Login screen from Tru64. Thats all I need to get VcXsrv see a Tru64 instance. Why would you want/need tunnelling ?

John M

Tunneling is becoming the normal method of using X11.

It also takes care of setting up the DISPLAY environment variable by default.

As I primarily use X-11 with OpenVMS, I never use xdmcp, so I do not use it.

Non-tunneled X11 is typically insecure as there is nothing preventing a hostile server on the network from accessing the screen/mouse/keyboard.