When I ssh into a headless Linux Mint 17 system, it doesn't create update / create an.Xauthority file. Moreover, when I run xauth I get the reply: marty@N40L ~ $ xauth xauth: file /home/marty/.Xauthority does not exist Using authority file /home/marty/.Xauthority xauth>exit marty@N40L ~ $ xauth xauth: file /home/marty/.Xauthority does not exist Using authority file /home/marty/.Xauthority xauth>It doesn't create the file. EDIT: When I connect monitor, then log in locally, the file is created but when I try to add an entry (because my SSH doesn't do it for me): marty@N40L ~ $ xauth list N40L/unix:0 MIT-MAGIC-COOKIE-1 34eee3b15cdb281021502d40dfba1cf2 localhost.localdomain/unix:0 MIT-MAGIC-COOKIE-1 34eee3b15cdb281021502d40dfba1cf2 marty@N40L ~ $ ls -d.X* -rw------- 1 marty marty 115 Sep 3 12:03.Xauthority marty@N40L ~ $ xauth generate $DISPLAY. PuTTY X11 proxy: wrong authorisation protocol attemptedxauth: (argv):1: unable to open display 'localhost:10.0'. Incidentally, doing a netstat --listen shows the port listening: tcp 0 0 localhost:6010 *:* LISTEN AGH, more info. I logged out of the X session on the server, and now the.Xauthority file has disappeared. It seems the file is ONLY there when logged in locally.

SSH connection stability. SSH users and owner of their system could first of all be sure to manipulate the SSH client configuration file. A.Xauthority file. Error with `ssh -Y`, error in locking authority file. (which is the only way you could not create the file. My guess is that the user's.Xauthority file. How to generate a new Xauthority with. A folder in /tmp however I don't know how to create a.Xauthority. Directory/files when logging in via SSH with. The remote tunnel end gets its own cookie; the remote ssh server generates it for you and puts it in ~/.Xauthority there. So, X authorisation with ssh is fully automatic. By the way, ssh is great in other ways too.

Can anyone tell me why, or how I can fix this? NEW DEVELOPMENT: I created a virgin user on the system called 'test'. I then logged in, and without ANY other commands, ran xeyes. Cost Drivers For Airline Industry In The Caribbean.

Which worked! Call Of Duty 4 Level 55 Save Game. So it's ONLY the user 'marty' that cannot xforward. How do I copy the settings from test to marty?

After finding out that it wasn't the system, by adding a test user (which x forwarding worked 'out the box'), I thought I'd start copying the.bash* startup files across to virginise the 'broken' user. None of the files were different, so next I deleted the users.ssh directory. When I ssh'd in, it moaned about 'Server refused our key', but I could log in using password. Once logged in, I could x forward perfectly.

I'll now try to setup the key again and see if I can get that working too. Then it'll be back to normal.

I have been given access to a system where I have no home folder. I've asked the administrator to create a home folder for me but due to some complexity he is unable to.

Therefore, I have no.Xauthority file and I cannot open a X11 gui. Is there a way for me to regenerate a.Xauthority file after login without root priv? I can change my env HOME and XAUTHORITY variable to a folder in /tmp however I don't know how to create a.Xauthority. I tried 'xauth generate:10. Trusted' but it says 'X11 connection rejected because of wrong authentication.' I am connecting via SSH to the server where I dont have a home folder from my client (running cygwin). I want to be able to connect back to the cygwin X server over SSH.

There is no content in HOME because HOME does not exist. I can set HOME to /tmp/mydir but only AFTER login. Steganos Security Suite 7.

I understand that.Xauthority is a 'shared secret' but doesn't it get generated at login? I had hoped I could rerun whatever program generates that file (after I have set HOME or XAUTHORITY to /tmp/mydir) – Jan 26 '17 at 13:26.