Timeline for How to forward X over SSH to run graphics applications remotely?
Current License: CC BY-SA 4.0
30 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 13, 2024 at 14:41 | history | edited | Gilles 'SO- stop being evil' | CC BY-SA 4.0 |
added 145 characters in body
|
| Feb 13, 2024 at 14:02 | review | Suggested edits | |||
| Feb 13, 2024 at 14:38 | |||||
| Jun 23, 2023 at 17:01 | comment | added | holzkohlengrill |
In case xclock works but other applications don't check out this answer: unix.stackexchange.com/a/709789/116710
|
|
| Apr 29, 2023 at 20:56 | review | Suggested edits | |||
| Apr 30, 2023 at 8:56 | |||||
| S Jun 30, 2021 at 19:38 | history | suggested | bryant1410 | CC BY-SA 4.0 |
Fix grammar
|
| Jun 30, 2021 at 19:01 | review | Suggested edits | |||
| S Jun 30, 2021 at 19:38 | |||||
| S Sep 27, 2019 at 16:53 | history | suggested | Nuno André | CC BY-SA 4.0 |
add links to specific options
|
| Sep 27, 2019 at 14:41 | review | Suggested edits | |||
| S Sep 27, 2019 at 16:53 | |||||
| S Nov 16, 2018 at 6:20 | history | suggested | qneill | CC BY-SA 4.0 |
Add some bolding, and a reason why the server won't say
|
| Nov 15, 2018 at 19:23 | review | Suggested edits | |||
| S Nov 16, 2018 at 6:20 | |||||
| S Aug 21, 2016 at 17:37 | history | suggested | goetz | CC BY-SA 3.0 |
fix broken links
|
| Aug 21, 2016 at 17:35 | review | Suggested edits | |||
| S Aug 21, 2016 at 17:37 | |||||
| Apr 11, 2015 at 14:32 | comment | added | x-yuri |
Pretty useful link. This exact issue prevented X11 Forwarding from working for me. I had ~/.ssh/rc file. And it turned it it's responsible for running xauth as such.
|
|
| May 29, 2014 at 17:18 | comment | added | Alexander Taylor |
after ssh -X run xterm & to get a graphical terminal as the ultimate test to see if it's working.
|
|
| Mar 11, 2014 at 13:08 | comment | added | Malkocoglu | Both machines are behind distinctive firewalls on distance locations, so no other port or connection available. However, I tried removing DISPLAY from AcceptEnv, it works as intended. I must have forgotten reloading sshd_config at some point so I mixed the results of two consequtive trials. For notation, out of the box configuration did not throw any error in -v mode but was not setting DISPLAY properly. | |
| Mar 11, 2014 at 10:42 | comment | added | Gilles 'SO- stop being evil' |
@Malkocoglu That's odd: DISPLAY is not transmitted from the client to the server, it's set on the server side, so it should not be in AcceptEnv. What value of DISPLAY do you get on the remote side? I suspect that your X connection isn't going through the SSH. Also I can confirm that X forwarding works out of the box on Ubuntu 13.10, without adding DISPLAY to AcceptEnv.
|
|
| Mar 11, 2014 at 10:29 | comment | added | Malkocoglu | For googlers: A Kubuntu 13.10 server and Kubuntu 13.10 client failed with "Cannot connect to X server". After investigating all other options, found that DISPLAY environment was not set automatically. So, adding DISPLAY to AcceptEnv in sshd_config solved my case. [AcceptEnv DISPLAY LANG LC_*] | |
| Jan 6, 2014 at 13:36 | comment | added | Gilles 'SO- stop being evil' |
@KhurshidAlam Your setup sounds fine, you can share the same keypair (it's purely a matter of security vs convenience). The permissions on .Xauthority have nothing to do with SSH. There's something unusual in your setup, post a new question and be sure to mention the permissions on .Xauthority (output of ls -l ~/.Xauthority), your distribution, and anything else that seems relevant.
|
|
| Jan 6, 2014 at 13:32 | comment | added | Khurshid Alam |
@Gilles Ok I deleted .Xauthority (as root) on server, now its working fine from one machine (machine-A).I have several computers (Desktops,Netbooks, Tablets). I share same private ssh-key across all machines (just copied the ~/.ssh). But now its showing same error when I try to connect to server from machine-B.I think permission set by a machine (on .Xauthority) during ssh -X doesn't really work for other machine with same ssh-key. I wonder, if there is a nice way to share same ssh-key pair across multiple computers.
|
|
| Jan 6, 2014 at 12:30 | comment | added | Gilles 'SO- stop being evil' |
@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/…
|
|
| Jan 6, 2014 at 8:10 | comment | added | Khurshid Alam |
@Gilles Is it still possible to use this method when server is already running a GUI environment? My home server is running basic gnome-panel classic & but when I try ssh -X user@server it gives me error: /usr/bin/xauth: /home/$user/.Xauthority not writable. Any idea why?
|
|
| Nov 13, 2013 at 7:48 | comment | added | puk |
+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.
|
|
| Apr 9, 2013 at 6:53 | comment | added | vasi | Thanks for mentioning xauth! Lack of that on a barebones server was causing me trouble. | |
| Aug 2, 2012 at 20:19 | comment | added | Gilles 'SO- stop being evil' |
@McKAMEY Yes, the client can be OSX. On the server (i.e. inside the SSH session), $DISPLAY is typically localhost:10 (the number can vary, it's the first free number starting at 10). If $DISPLAY is set in the ssh session, everything should work. If it doesn't, you can ask here; be sure to describe exactly what you did (contents of .ssh/config, command line, etc.), and say precisely what is wrong (copy-paste any error message).
|
|
| Aug 2, 2012 at 19:21 | comment | added | McKAMEY |
Is this answer valid if the client is Mac OS X? It doesn't seem to be working, just sends display to localhost:10.
|
|
| May 6, 2011 at 23:52 | comment | added | user unknown | Thanks, gilles. Since it was a 192.168.*-address, everybody in the net (eth-xlink-cable) was pretty trustworthy. :) | |
| May 6, 2011 at 22:52 | comment | added | Gilles 'SO- stop being evil' |
@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.
|
|
| May 6, 2011 at 22:33 | comment | added | user unknown |
Don't we need sometimes to set sudo xhost +client? When I connect from xubuntu1 to xubuntu2, xubuntu2 running sshd, I do ssh -X from 1, on 2 I type above xhost-command, and then I start a graphical program. Is it a workaround if no modificaton of /etc/*config is wanted?
|
|
| May 6, 2011 at 20:37 | vote | accept | Mr. Shickadance | ||
| May 6, 2011 at 20:26 | history | answered | Gilles 'SO- stop being evil' | CC BY-SA 3.0 |