| [sgt] / putty-wishlist / data / portfwd-at-start |
Another missing </em>
Almost _all_ of the final connection-layer loop, in both SSH1 and SSH2, is now handled by the packet dispatch table. Dispatch table entries are enabled as soon as possible, so that if anyone tries to (for example) start using a forwarded port before the main shell session setup has finished, things should work sensibly. The SSH code is now a hybrid of coroutine-based sequential logic and table-driven event dispatch, each where it makes the most sense. I'm rather pleased with it. Should fix: ext-data-at-start, portfwd-at-start.
CVS revision numbers, stored as `cvs2svn:cvs-rev' properties, are a useful piece of history in this repository but we don't want to preserve their latest values on future commits. Accordingly, I'm deleting them from all active development (though not from past release branches).
Summary: "unexpected packet type 95" with VShell 2.1.5 New (old) failure mode at startup. Sounds strongly similar to `portfwd-at-start' so cross-linked. Also updated the latter with the latest report.
Summary: "unexpected packet type 91" with tunnel open during connection setup
|
CVS Admin Powered by ViewCVS 1.0-dev |
ViewCVS and CVS Help |