Home
|
FAQ
|
Feedback
|
Licence
|
Updates
|
Mirrors
|
Keys
|
Links
|
Team
Download:
Stable
·
Snapshot
|
Docs
|
Changes
|
Wishlist
Better handling of the connection closing, and of SSH_MSG_DISCONNECT being received. Ideally we should maintain our own idea of when and whether we expect to see a closure, and only signal clean exit when a closure or disconnect arrives that we were expecting. If one arrives unexpectedly it should count as an ungraceful closure, display a dialog box containing the text out of MSG_DISCONNECT, and not close the window unless the user selected "Always".
SGT, 2005-01-11: In fact, SSH is really simple in this respect: as far as I can tell it's always the client's job to close the connection, so any closure on the part of the server counts as unexpected. Unless, that is, it comes after a DISCONNECT.