-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-X X11 fowarding failure #1593
Comments
Related #1563. Workaround: Set |
@hakasapl - Please confirm if the PR changes has fixed your issue. |
The |
Can you share a -vvv log with the new issue too? Feel free to redact any hostnames and cookies. Thanks! |
Sure! I reverted to the natively installed windows openssh to see if that would make a difference, but it didn't. I am also using XWin from Cygwin now to test out some different X servers, but both x servers show the same error in the log.
It seems there is only two lines relevant to the X11 forwarding setup. And here's my xauth info in my
|
@hakasapl Thanks for the dump. I'll have to check Cygwin, but I suspect xauth there has the same quirk as VcXsrv in that it doesn't understand the Is your |
Same issue unfortunately after resetting the display environment var. It is currently set to
|
@hakasapl Can you provide a dump of |
Nothing printed
|
@hakasapl Thanks, I'm setting up a Cygwin xauth test now and will get back to you shortly. |
@hakasapl So this works for me here, few more questions:
|
XAuth version is Yes,
That may be the root cause here. I verified the X-server was running on 127.0.0.1:0.0 and listening tcp. |
@hakasapl Ah. Is this with Xwin? Try switching back to Vcxsrv if possible. I've used that successfully. I'll install Xwin and try reproducing this now. |
@hakasapl Can confirm Cygwin/X doesn't support untrusted forwarding per FAQ https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trusted-untrusted-x11-forwarding |
With Vcxsrv it still had the same log message, except it uses Vcxsrv xauth now. When I tried to manually generate, I don't get an error this time (I did with cygwin), but |
@hakasapl Thanks for your patience, there are a bunch of bugs interacting with each other that are likely impacting you here. Can you post a new log dump? I have Vcxsrv working here, so we just need to compare notes. |
Sorry, I won't be able to take a look at this for a few days, but I'll get back to you with a dump soon. |
@hakasapl any updates? |
@hakasapl ping |
Troubleshooting steps
TEMP
andTMP
environment vars toC:\Temp
"OpenSSH for Windows" version 8.1.0.0
Server OperatingSystem Ubuntu 18.04.4 Server
Client OperatingSystem Windows 10 Pro
What is failing
I can't seem to get the
-X
option to work with my local X server (VcXsrv). There are a few errors indicated below about the exact errors. The-Y
option works just fine, but I'd rather not use that due to security issues. I've been able to reproduce this bug on multiple windows installations.Expected output
Successful secure X11 forwarding
Actual output
First Case: When I add xauth to my path (as mentioned above), and use the
-X
flag, I get this message:Second Case: When I manually add the xauth location to my
~/.ssh/config
file, I get the messageThe text was updated successfully, but these errors were encountered: