Hi Jack. ssh -Y ended up with me doing the following:
$ /usr/X11R6/bin/xauth list 127.0.0.1:0.0
/usr/X11R6/bin/xauth: creating new authority file /home/phil/.Xauthority
Nothing happened on the other xterm window, so I went looking for
/home/phil/.Xauthority - it didn't exist! (yes, I typed ls -a) :)
So I tried ssh -X ... and ended up with me doing the following:
$ /usr/X11R6/bin/xauth -f /tmp/ssh-Q7ut6XsxFY/xauthfile generate
127.0.0.1:0.0 MIT-MAGIC-COOKIE-1 untrusted timeout 1200
/usr/X11R6/bin/xauth: creating new authority file
/tmp/ssh-Q7ut6XsxFY/xauthfile
now a file called "xauthfile" was created in that directory, and its
contents were:
0MIT-MAGIC-COOKIE-1&<12 character long pseudorandom string>
But still, no movement on the xterm window.
Here's the oddity:
Why could I just start the Cygwin/X server and run putty for windows
with X11 forwarding and it'll work just fine?
Why would X-Win32 with its built-in StarnetSSH client work just fine
completely on its own?
Somebody else posted that ZoneAlarm jumps in the way of Cygwin's OpenSSH
- even if ZoneAlarm is shut down, but I have a hard time believing
that's the issue...
- Phil
Jack Tanner wrote:
No, it should be on the local computer. Try this: run startxwin.bat,
then open two xterms. In one, run the ssh -Y -vv ... command. When it
freezes, in the other xterm try to run the xauth command by hand.
By the way, I gave you the wrong command syntax below. That should've been
$ /usr/X11R6/bin/xauth -f /tmp/ssh-WHATEVER/...
If I'm wrong, and it is on the remote computer, then from the second
xterm you should be able to ssh in without X forwarding, and try it on
the remote machine.
Philip H. Schlesinger wrote:
That appears to be something generated on the fly - and by the looks
of it, on the remote computer, as that directory doesn't exist.
- Phil
Jack Tanner wrote:
Philip H. Schlesinger wrote:
Jack Tanner wrote:
>> debug2: x11_get_proto: /usr/X11R6/bin/xauth -f
>> /tmp/ssh-zfHmWgkGRG/xauthfile generate 127.0.0.1:0.0
>> MIT-MAGIC-COOKIE-1 untrusted timeout 1200 2>/dev/null
>
> 1) What do you get if you try that by command hand (sans the
/dev/null
> redirection)?
Not sure what you mean here...forgive my n00b-ness...
Err, that should've said "try that command by hand". As in,
$ /tmp/ssh-WHATEVER/xauthfile generate [...] timeout 1200
(Drop the 2> /dev/null bit at the end, thus keeping the output from
xauthfile from being redirected to /dev/null.)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
