![]() If you are someone who reads the full message that ssh spits back at you, the answer will be immediately obvious to you. X11 forwarding is disabled to avoid man-in-the-middle attacks. Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks. Password authentication is disabled to avoid man-in-the-middle attacks. ![]() Offending RSA key in /home/jdoe/.ssh/known_hosts:71 Of course, the remote server should allow X11forwarding.Īnother case I ran into where ssh will refuse to carry over the DISPLAY variable setting even when you use ssh -X: $ ssh -X WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!Īdd correct host key in /home/jdoe/.ssh/known_hosts to get rid of this message. Xauthority file but since I don't know much about this I won't go any further.Ĭonclusion: from the three cases above, we can confirm that in order for remote X Windows to be displayed properly, both 1. From what I know, this is related with MIT-MAGIC-COOKIE in the. The xclock is successfully shown in my local machine.Īgain, check out the result of setenv | grep DISPLAY in this case. ![]() With this setting, xclock works!! here's a screenshot to prove that I'm not lying. Warning: No xauth data using fake authentication data for X11 forwarding. Warning: untrusted X11 forwarding setup failed: xauth key data not generated ![]() This time, I will properly specify the DISPLAY variable at the local machine and also ssh to remote server with my -X switch on. I'm not sure how this difference is caused but I'm getting a hunch that its related to whether you've satisfied either condition 1. on the other hand, the result of case1 to this command line is DISPLAY: undefined variable. *A different outcome with setenv | grep DISPLAY can be seen here(compare with case1). But even so, after ssh'ing(without the -X switch) the xclock is not executed. Last login: Tue Jun 24 22:33:32 2014 ~]$ xclockĮrror: Can't open ~]$ setenv | grep ~]$Īt the start you can see that I have properly set the DISPLAY variable. But when I'm ssh'ing, I won't turn on the -X switch. This time, at the local machine, I will specify the DISPLAY variable. Last login: Tue Jun 24 22:23:13 2014 ~]$ xclockĮrror: Can't open ~]$ setenv | grep $DISPLAYĪs you can see an error Error: Can't open display: is shown at the remote server terminal. # the blank means that DISPLAY variable has not been ~ And then I will ssh to remote server with -X switch and then try executing xclock. My local machine will have no DISPLAY variable set. My previous attempts lack one or both of these two conditions.Īnyhow, for later users who see this here's are examples to show you what I'm trying to say. ![]() when ssh'ing to remote server, the -X switch must be on.the DISPLAY variable should be properly set.based on your comments I was able to figure out the problem. As for the attempt written on the upper part, the commands were typed in at Cygwin terminal. my local computer is Windows 7 so I have Xming running on background in order to allow X11 display. The weird thing is that if I connect to the remote server through my PUTTY and repeat the command 'firefox' it works?!?!(firefox is displayed on local computer) What does the 'no display speicified' error mean? Even without the -X, -Y switches, my attempt failed. I used -X, -Y because I read somewhere that these two options are related with credentials regarding X11 and these switches will do the job for me. the below are my attempts to open firefox ~ I have logged in to a remote server and am trying to display an x application(e.g. ![]()
0 Comments
Leave a Reply. |