| Summary: | TTSSH will not connect to OpenSSH_3.4p1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Ari Gordon-Schlosberg <mindrot> | ||||
| Component: | sshd | Assignee: | OpenSSH Bugzilla mailing list <openssh-bugs> | ||||
| Status: | CLOSED WORKSFORME | ||||||
| Severity: | normal | CC: | mindrot | ||||
| Priority: | P2 | ||||||
| Version: | -current | ||||||
| Hardware: | ix86 | ||||||
| OS: | NetBSD | ||||||
| Attachments: |
|
||||||
|
Description
Ari Gordon-Schlosberg
2002-07-24 12:12:30 AEST
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 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. 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. Created attachment 143 [details]
Patch to add pid to logs
This is a quick patch to display the pid of the logging process. It may be
helpful in debugging privsep problems.
Please retest with a recent release, some of the older releases had OpenSSL issues. Just tried this with OpenSSH -current linked against OpenSSL 0.9.7b (using blowfish cipher) and it worked OK. Please re-open if you can reproduce with current OpenSSH and OpenSSL versions. Mass change of RESOLVED bugs to CLOSED |