This is the mail archive of the
mailing list for the Cygwin project.
RE: After updating Cygwin installation on 29-05-2015 , cygwin-x server does not accept ssh x11 forwarding any more
- From: <Robert dot Atwood at diamond dot ac dot uk>
- To: <cygwin at cygwin dot com>
- Date: Fri, 29 May 2015 17:49:41 +0000
- Subject: RE: After updating Cygwin installation on 29-05-2015 , cygwin-x server does not accept ssh x11 forwarding any more
- Authentication-results: sourceware.org; auth=none
- References: <6CCDD8FC6578314C902BBF87D511D9D89B211236 at EXCHMBX01 dot fed dot cclrc dot ac dot uk> <33284267 dot 20150529200559 at yandex dot ru>
> -----Original Message-----
> From: Andrey Repin [mailto:email@example.com]
> Sent: 29 May 2015 18:06
> To: Atwood, Robert (DLSLtd,RAL,SCI); firstname.lastname@example.org
> Subject: Re: After updating Cygwin installation on 29-05-2015 , cygwin-x
> server does not accept ssh x11 forwarding any more
> Greetings, Robert.Atwood@diamond.ac.uk!
> > After updating Cygwin installation on 29-05-2015 , cygwin-x server
> > does not accept ssh x11 forwarding any more.
> > I do not modify the configuration files.
> > I generally start Xwin server using the icon, launch a console to
> > remote server using Putty configured with X11 forwarding, then launch X11
> program from that console.
> > Now I find that if I start Xwin by xinit, run ssh from inside the Xwin
> > terminal box , even then it does not work, the connection of Prior to
> > today it was always working , and has been for several years.
> > What has changed ?
> X server not listening on TCP anymore, to begin with.
Thanks for clarifying that. However, I lack the technical knowledge to interpret this correctly.
A long time ago I used to use insecure X-window without ssh forwarding and in that case it was necessary
to listen on tcp for incoming X connections from another machine, I have no idea that the local-end of the ssh tunnel
actually uses tcp on the local host? Is that what's happening?
Using -listen tcp only works now if I also install xhost and then use xhost + which seems extreme?
At least it demonstrates that it is authorization and not some other problem.
I am afraid that searching had turned up rather instances of people's virus software interfering.
> Please use search, you're, like, fifth to ask this question.
The only clue is in
But, it's not very clear about what the change is, or when it occurred.
As I say , that does not immediately work for me, until I think back to insecure clusters (why bother if it is not connected to the internet?) of many years ago and try xhost +
But several other results
are unrelated it seems.
> > [kny48981@i12-ws011 ~]$ xeyes
> > debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max
> > 16384
> > debug1: client_request_x11: request from ::1 49318
> > debug1: channel 1: new [x11]
> > debug1: confirm x11
> > debug1: channel 1: free: x11, nchannels 2 Invalid MIT-MAGIC-COOKIE-1
> > keyError: Can't open display: localhost:13.0
> > [kny48981@i12-ws011 ~]$
> With best regards,
> Andrey Repin
> Friday, May 29, 2015 20:03:24
> Sorry for my terrible english...
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple