mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-04-17 11:08:06 -05:00
5fdce31eca
Now we always respond to backend disconnection or connection_fatal by calling plug_closing. And we always do it in a toplevel callback, so that when the Plug responds by calling our Socket close method (which frees us), nothing re-entrant happens. Also, the handling of notify_remote_disconnect is brought into line with the spec in putty.h, which says it can be sent redundantly (when already disconnected) or spuriously (when not even disconnected at all), so the toplevel callback queued by that method will check first. After this change, failures during connection_setup are now handled _mostly_ sensibly: if the proxy connection fails, then the main connection gets enough information to pass a sensible connection_fatal on to the real front end. This also fixes the assertion failure mentioned in the TODO comment, replacing it with a reasonably sensible connection_fatal() - although I still think that in that situation it might be better not to have a dialog box at all.
This is the README for PuTTY, a free Windows and Unix Telnet and SSH
client.
PuTTY is built using CMake <https://cmake.org/>. To compile in the
simplest way (on any of Linux, Windows or Mac), run these commands in
the source directory:
cmake .
cmake --build .
Documentation (in various formats including Windows Help and Unix
`man' pages) is built from the Halibut (`.but') files in the `doc'
subdirectory using `doc/Makefile'. If you aren't using one of our
source snapshots, you'll need to do this yourself. Halibut can be
found at <https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is
https://www.chiark.greenend.org.uk/~sgtatham/putty/
If you want to send bug reports or feature requests, please read the
Feedback section of the web site before doing so. Sending one-line
reports saying `it doesn't work' will waste your time as much as
ours.
See the file LICENCE for the licence conditions.