[coLinux-devel] [ colinux-Bugs-2748015 ] PuTTY failing after a while with "Server key not valid"

[SourceForge.net <no...@so...>]

Bugs item #2748015, was opened at 2009-04-09 15:54
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2748015&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Daemons (Windows)
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: PuTTY failing after a while with "Server key not valid"

Initial Comment:
Hi,
a few days ago I upgraded my coLinux install to version 0.8.0 snapshot 20090329.
While using the ndis-bridge feature I noticed my SSH connections crashing after a while (like 20 minutes, sometimes less, sometimes after hours).

PuTTY and WinSCP report the error as "Server's host key did not match the signature supplied".
WinSCP is build on the SSH code of PuTTY so it seems to be a low-level error.

I tested a few setups to isolate the problem:
- coLinux 0.8.0 (20090329) with ndis-bridge: fails after a while.
- coLinux 0.8.0 (20090329) with pcap-bridge: fails after a while.
- coLinux 0.7.4 rc1 (20090329) with ndis-bridge: fails after a while.
- coLinux 0.7.4 rc1 (20090329) with pcap-bridge: fails after a while.

- coLinux 0.7.3 (20080608) with pcap-bridge: still going strong after 2 hours and alot of traffic.

The fact that I get the same error with the RC1 and the 0.8.0 development version is not supprising as it should be based on the same code.

>From searching the net I found these possible causes for the problem:
- The cached server key signature is not valid anymore (would prevent me from logging in)
- The network traffic gets mauled between server and client
- The client or server software can be at fault.

My setup specs:
- AMD AthlonXP 3800+, 2gb ram
- Windows XP Pro SP3 + all updates to date
- Network card: NVIDIA nForce 10/100/1000 Mbps Ethernet
- Guest OS is ArchLinux (ver 2009.02) (using only prebuild packages from the ArchLinux repositories)
- Server software: OpenSSL (0.9.8j pacman package #1) / OpenSSH (5.1p1 pacman package #2)
- Client software: PuTTY (0.60) / WinSCP (4.1.7 build 413)

I tested the virtual machine on the windows host system. There cannot be any signal decay on the wire cause the bridged network shouldn't use it. This, and the fact I cannot reproduce the problem with version 0.7.3, leads me to believe the newer colinux versions are corrupting the data somewhere in between.

I would like to know what you make of this problem. Solutions/workarounds and reproducability confirmations are also welcome.

Thanks, Keith

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2748015&group_id=98788