mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-05-28 23:34:49 -05:00

Revision 1b2f39c24bb6591a4192377d9393f5c3e45cb5bd introduced guards to use the built-in defaults in the event that the SESSKEY was null. This was later reverted in 39c20d4819794417e4e84429d1eb5430e3865b25 because (a) a null SESSKEY is precisely how the absence of a per-session configuration file is signalled to the backend, and (b) everything could apparently already cope with a null SESSKEY anyway. Unfortunately, in between these, 3214563d8ed7469e20d4ffdddd55c430334ce803 introduced new functions for handling boolean-valued settings. The reversion didn't affect the new `gppb_raw' function, which retained the erroneous guard against null SESSKEY. In consequence, PuTTY ignores X resources and `-xrm' settings unless `~/.putty/sessions/Default%20Settings' exists, causing undesirable behaviour such as starting login shells, establishing `utmp' entries, scrolling on output, failing to scroll on keypress, not blinking the cursor, etc. This isn't a total disaster: touching `~/.putty/sessions/Default%20Settings' makes the problem go away. But it seems worth fixing anyway. Apply the obvious one-line fix. Signed-off-by: Mark Wooding <mdw@distorted.org.uk>
PuTTY source code README ======================== This is the README for the source code of 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), the general method is to run these commands in the source directory: cmake . cmake --build . These commands will expect to find a usable compile toolchain on your path. So if you're building on Windows with MSVC, you'll need to make sure that the MSVC compiler (cl.exe) is on your path, by running one of the 'vcvars32.bat' setup scripts provided with the tools. Then the cmake commands above should work. 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. 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.
Description
Languages
C
89.7%
Python
8%
Perl
0.9%
CMake
0.8%
Shell
0.4%
Other
0.1%