Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

17
  • 52
    @user: No, you never need xhost +. xhost is from a gentler era when having a machine connected to the network meant you were trustworthy. xhost + means anyone who can spoof your IP can take control of your X server session. ssh -X will set up all the required authorizations. If X11 forwarding disabled in the server config, talk to your administrator; if that doesn't work, see Forwarding X11 over SSH if the server configuration doesn't allow it. Commented May 6, 2011 at 22:52
  • 10
    Thanks for mentioning xauth! Lack of that on a barebones server was causing me trouble. Commented Apr 9, 2013 at 6:53
  • 5
    +1 for making the distinction between ~/.ssh/config and /etc/ssh/sshd_config in the same place. I could not tell if they were different' files or just a change in nomenclature. Commented Nov 13, 2013 at 7:48
  • 1
    @KhurshidAlam It doesn't matter whether the server is also running a GUI environment. Check the permissions on the .Xauthority file. If using Red Hat or other system with SELinux, check the SELinux context, see unix.stackexchange.com/questions/36540/… Commented Jan 6, 2014 at 12:30
  • 13
    after ssh -X run xterm & to get a graphical terminal as the ultimate test to see if it's working. Commented May 29, 2014 at 17:18