bugzilla-daemon at mindrot.org
2002-Jul-24 02:16 UTC
[Bug 368] TTSSH will not connect to OpenSSH_3.4p1
http://bugzilla.mindrot.org/show_bug.cgi?id=368 ------- Additional Comments From mindrot at regs.nebcorp.com 2002-07-24 12:16 ------- Just make life easier: TeraTerm 2.3 http://hp.vector.co.jp/authors/VA002416/ttermp23.zip TTSSH 1.5.4 plugin http://www.cs.cmu.edu/~roc/ttssh154.zip ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Jul-25 10:04 UTC
[Bug 368] TTSSH will not connect to OpenSSH_3.4p1
http://bugzilla.mindrot.org/show_bug.cgi?id=368 ------- Additional Comments From markus at openbsd.org 2002-07-25 20:04 ------- it looks like the monitor process is sending data over the network. you could change packet.c to printout the current pid and the packet type for every packet sent. the monitor process is not allowed to call packet_send. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Aug-06 02:29 UTC
[Bug 368] TTSSH will not connect to OpenSSH_3.4p1
http://cvs-mirror.mozilla.org/webtools/bugzilla/show_bug.cgi?id=368 mindrot at doyle.nebcorp.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mindrot at doyle.nebcorp.com ------- Additional Comments From mindrot at doyle.nebcorp.com 2002-08-06 12:29 ------- This occurs when using the blowfish cypher (see the ttssh debug output) with the openssh 3.4 client on a FreeBSD 4.4 machine, linked against openssl 0.9.6e. It does not occur when using the default 3DES cypher. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.