Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Created By | dick.kniep@lindix.nl Summary | Cannot log on using ssh-proxy Queue | pyhoca-gui Version | HEAD Type | Bug State | Unconfirmed Priority | 3. High Operating System | 9 Owners | ------------------------------------------------------------------------------ dick.kniep@lindix.nl (2011-05-30 15:21) wrote: Using a key that is working on Ubuntu, on windows I get a "host key for server lindix.cvix.nl does not match" while trying to connect.
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Summary | Cannot log on using ssh-proxy Queue | pyhoca-gui Version | HEAD Type | Bug -State | Unconfirmed +State | Assigned Priority | 3. High Operating System | 9 -Owners | +Owners | Mike Gabriel ------------------------------------------------------------------------------ Mike Gabriel <mike.gabriel@das-netzwerkteam.de> (2011-05-31 11:11) wrote: For testing, please move %USERPROFILE%/.ssh/known_hosts out of the way. The occurring error refers to a mismatch of SSH host keys. If you are using SSH Proxy you probably connect to [localhost]:<port>. If you have used <port> for another target machine already (i.e. in another session profile using SSH Proxy) then this error will occur. I will leave this bug open, as it needs some GUI guidance in case such a situation happens to the user.
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | dick.kniep@lindix.nl Summary | Cannot log on using ssh-proxy Queue | pyhoca-gui Version | HEAD Type | Bug State | Assigned Priority | 3. High Operating System | 9 Owners | Mike Gabriel ------------------------------------------------------------------------------ dick.kniep@lindix.nl (2011-06-01 18:33) wrote: Hi Mike, Off course this was very smart of me....... (cynical) However now I have another problem that seems to be introduced with the last version. The version works beautifully on Linux. However on Windows XP I get the following message: "Error reading SSH protocol banner [Errno 10054] The external host has ended the connection" I didn't trust my judgement so I asked my own network specialist to investigate this. He found some references to this error with Paramiko. It looks like the windows machine is closing the port. Furthermore with the older pyhoca-gui it still works. So something has changed and is causing this problem
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Summary | Cannot log on using ssh-proxy Queue | pyhoca-gui Version | HEAD Type | Bug State | Assigned -Priority | 3. High +Priority | 2. Medium -Operating System | 9 +Operating System | 0 Owners | Mike Gabriel ------------------------------------------------------------------------------ Mike Gabriel <mike.gabriel@das-netzwerkteam.de> (2011-06-09 23:31) wrote: The reported error also occurs on GNU/Linux machines. The error means that the SSH proxy connection could be set up, but the target X2go server could not be reach by SSH. If the error occurs, please try if you can use SSH/PuTTY for hopping to the SSH proxy host and from there to the X2go server. If that works while PyHoca-GUI fails, I'll have to take another look. Thanks, Mike
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | dick.kniep@lindix.nl Summary | Cannot log on using ssh-proxy Queue | pyhoca-gui Version | HEAD Type | Bug State | Assigned Priority | 2. Medium Operating System | Owners | Mike Gabriel +New Attachment | windows-denied.txt ------------------------------------------------------------------------------ dick.kniep@lindix.nl (2011-06-16 16:33) wrote: Hi Mike, We tested with Putty. There the tunnel works. Also, it works from Linux.
The reported error also occurs on GNU/Linux machines.
The error means that the SSH proxy connection could be set up, but the target X2go server could not be reach by SSH.
If the error occurs, please try if you can use SSH/PuTTY for hopping to the SSH proxy host and from there to the X2go server.
If that works while PyHoca-GUI fails, I'll have to take another look.
Thanks, Mike
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | dick.kniep@lindix.nl Summary | Cannot log on using ssh-proxy Queue | pyhoca-gui Version | HEAD Type | Bug State | Assigned Priority | 2. Medium Operating System | Owners | Mike Gabriel +New Attachment | linux-success.txt ------------------------------------------------------------------------------ dick.kniep@lindix.nl (2011-06-16 16:35) wrote: Included is another log file from auth.log
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | dick.kniep@lindix.nl Summary | Cannot log on using ssh-proxy Queue | pyhoca-gui Version | HEAD Type | Bug State | Assigned Priority | 2. Medium Operating System | Owners | Mike Gabriel +New Attachment | pyhoca-gui.exe.log ------------------------------------------------------------------------------ dick.kniep@lindix.nl (2011-06-16 16:37) wrote: And the debug output from pyhoca-gui
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Summary | Cannot log on using ssh-proxy Queue | pyhoca-gui Version | HEAD Type | Bug -State | Assigned +State | Feedback Priority | 2. Medium Operating System | Owners | Mike Gabriel ------------------------------------------------------------------------------ Mike Gabriel <mike.gabriel@das-netzwerkteam.de> (2011-06-18 21:07) wrote: Your SSH proxy setup in the session profile looks weird: sshproxy_host: lindix.cvix.nl:3389 sshproxy_tunnel: 127.0.0.1:3389:localhost:3389 I know about your dual SSH auth mechanism. Do both SSH daemons (the one with key auth and the one with password auth) use the same port, but just another interface? This is confusing me... Please thoroughly check your session profile configs. Mike
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Summary | Cannot log on using ssh-proxy -Queue | pyhoca-gui +Queue | python-x2go -Version | HEAD +Version | HEAD Type | Bug State | Feedback Priority | 2. Medium Operating System | Owners | Mike Gabriel ------------------------------------------------------------------------------ Mike Gabriel <mike.gabriel@das-netzwerkteam.de> (2011-06-19 23:30) wrote: I have found out what happens here: Paramiko mixes IPv4 and IPv6. If you specify a hostname like localhost, Paramiko will prefer IPv6 (::1). But the SSH proxy tunnel ends at an IPv4 address (127.0.0.1). These two do not have anything to do with each other. I'll have to think about a clean solution for this, as a work-around please use »127.0.0.1« instead of the hostname »localhost«.
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=70 ------------------------------------------------------------------------------ Ticket | 70 Updated By | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Summary | Cannot log on using ssh-proxy Queue | python-x2go Version | HEAD Type | Bug -State | Assigned +State | Resolved Priority | 2. Medium Operating System | 10 Owners | Mike Gabriel ------------------------------------------------------------------------------ Mike Gabriel <mike.gabriel@das-netzwerkteam.de> (2011-06-27 07:48) wrote: This should be fixed in release >= 0.1.1.0.
-
bugs＠x2go.org