Send us a question or comment

<< Previous
Next >>

I was using X11 forwarding with an earlier 3.x version of SecureCRT, and had no problems displaying X11 clients on my PC-based X server; now I'm using SecureCRT 3.3 and I am getting a warning in my session windows on the remote server when I try to start my X11 clients.

Between 3.2 and 3.3, a significant change was made in how X11 MIT-MAGIC-COOKIEs are checked by SecureCRT when an X client connection is requested over a forwarded X11 connection.

In SecureCRT 3.3, the mechanism for checking MIT-MAGIC-COOKIEs was changed.

On the SSH server, if you type:

% xauth list

at your shell prompt, you should get a list of the valid X11 cookies that the user you are logged in as on the remote server. In the list, you should see lines of the form:

sshserver.com:10 MIT-MAGIC-COOKIE-1 9c15e979c1ba2ed4106142d97ac5e513
sshserver/unix:10 MIT-MAGIC-COOKIE-1 9c15e979c1ba2ed4106142d97ac5e513

The sshserver.com:10 should correspond to the value set for your DISPLAY variable set on the SSH server at logon time

If you do not see a cookie matching this, then in all likelihood xauth is either not configured or not running properly on the remote SSH server.

<< Previous
Next >>

1.  Read or download one of our secure solutions white papers. 2.  Download a free
30-day evaluation copy of our products.
3.  Let us help define the right Secure Shell solution for your company. 4.  Subscribe to our monthly newsletter for tips, solutions ideas, and product news.