
Remote X clients will not display, via PuTTY or Plink, without a correct localhost entry in /etc/hosts on the remote machine. Linux hint: you will also need this line in /etc/pam.d/su to forward xauth keys between users when calling su Also use pam_xauth to automatically forward xauth cookies between users when using su. If you are connecting to an Ubuntu Server Edition: you need package xauth installed for X-Forwarding to work. either build '-with-default-path=etc:etc' or use environment files in '~/.ssh'). If a program displays from a PuTTY console but not from Plink then the default user PATH may need configuring/changing for the remote sshd server so that ssh can find it (e.g. Warning: I recommend you do not alter DISPLAY on the remote terminal, when using X-Forwarding.you may end up with working, but unencrypted, connections to a server!īoth XLaunch and Xmingrc make starting an X client via Xming's Plink easy. On that remote terminal, DISPLAY is automatically set to point at display 10 or above when X-Forwarding Use PuTTY to get a remote terminal on your Windows desktop and from that run the X clients you need, or run X clients via Plink using a stored session or a command. I recommend using both PuTTYgen and Pageant in that process as well as setting up some PuTTY Saved Sessions. You may therefore need to also add this to sshd_config AddressFamily inet Getting Xming-portablePuTTY (or standard PuTTY) working first, before using Plink, XLaunch or Xming, is always a good idea. XAuthLocation /usr/bin/X11/xauth this last keyword-argument pair maybe needed on AIXĭue to a bug in OpenSSH: disabling (or badly configuring) IPv6 on Linux/Unix can mess up X-Forwarding. Use PuTTY with SSH and X-Forwarding and enable it in the sshd server on the remote machine i.e. X-Forwarding If you use X-Forwarding: you don't need to directly use xhost/xauth or set a DISPLAY variable.using xhost or xauth and especially working via the defunct Telnet or Rsh/Rlogin protocols). The X protocol network traffic is only encrypted if using X-Forwarding with SSH and this is therefore the recommended method for access control, all others method are potentially unsafe (e.g. be careful as they grant access to everyone.

Access control Only use Xming option -ac or 'xhost +' on trusted networks, never on public ones i.e.
