mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-04-15 01:58:05 -05:00
138df73e81
A user reports that if the Print Spooler service is disabled via services.msc, then PuTTY can report 'Out of memory!' when you try to open the Terminal config pane, which is the one containing the combo box enumerating the available printers. Apparently this is because the call to EnumPrinters failed with the error code other than the expected ERROR_INSUFFICIENT_BUFFER, and in the process, left garbage in the pcbNeeded output parameter. That wouldn't be too surprising if it had simply _not written_ to that parameter and therefore it was never initialised at all in the calling function printer_add_enum. But in fact, printer_add_enum *does* precautionarily initialise needed=0 before the initial call to EnumPrinters. So EnumPrinters must have actively written one of its *own* uninitialised variables into it! Anyway, the obvious fix is to distinguish ERROR_INSUFFICIENT_BUFFER from any other kind of EnumPrinters failure (in fact turning off Print Spooler seems to lead to RPC_S_SERVER_UNAVAILABLE), and not attempt to proceed in the case of other failures.
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 .
Then, to install in the simplest way on Linux or Mac:
cmake --build . --target install
On Unix, pterm would like to be setuid or setgid, as appropriate, to
permit it to write records of user logins to /var/run/utmp and
/var/log/wtmp. (Of course it will not use this privilege for
anything else, and in particular it will drop all privileges before
starting up complex subsystems like GTK.) The cmake install step
doesn't attempt to add these privileges, so if you want user login
recording to work, you should manually ch{own,grp} and chmod the
pterm binary yourself after installation. If you don't do this,
pterm will still work, but not update the user login databases.
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.