Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Whenever I ssh with X11 forwarding to a remote box from my macbook I get the following error after a few seconds pause:

Warning: untrusted X11 forwarding setup failed: xauth key data not generated
Warning: No xauth data; using fake authentication data for X11 forwarding.

Any ideas on how to fix this?

share|improve this question

Take a look at

share|improve this answer
Welcome at Super User! But, please consider Are answers that just contain links elsewhere really “good answers”? Enjoy! – Arjan May 8 '10 at 19:00
If they point you to good information, I think they are. – bryan May 8 '10 at 19:33
I think that at the very least, use a block quote to include an excerpt from said linked page that may answer the question. – fideli May 9 '10 at 3:50

Well, I took a look at @bryan's answer and the succinct answer he proposed. My interpretation of it is thus. First, the behavior is caused by the use of the -X flag. From the text,

The warning can be silenced by using ssh -Y, since that is what ssh -X is doing now anyway.

For an explanation of why that may work, read the link. Specifically, the reasoning behind these warnings is

Trusted X11 forwarding means that you trust the server that you wish to ssh into is not using any keyloggers, screenshot utilities, packet sniffers, or anything else to hijack your connection, in which case X11 will allow it to do whatever a local client would be able to do.

so the -Y is providing this level of trust to avoid warnings. However, that may not be sufficient. I, for example, was trying to silence this message on a Rocks cluster where changes had to be done at the configuration level. You can also silence it via the ssh_config file. According to this link you can add

ForwardX11Trusted yes

into /etc/ssh/ssh_config. However there are ramifications to doing so. I am running on a secure, private network so the concerns are limited. I will also probably do this on my laptop as well, but I never said I fully understood the concerns myself! If you can express why this may still be risky (I only ssh into computers I know fairly well) then please help clarify in comments.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .