mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-10 01:48:00 +00:00
67d3791de8
With this change, we stop expecting to find putty.chm alongside the executable file. That was a security hazard comparable to DLL hijacking, because of the risk that a malicious CHM file could be dropped into the same directory as putty.exe (e.g. if someone ran PuTTY from their browser's download dir).. Instead, the standalone putty.exe (and other binaries needing help) embed the proper CHM file within themselves, as a Windows resource, and if called on to display the help then they write the file out to a temporary location. This has the advantage that if you download and run the standalone putty.exe then you actually _get_ help, which previously didn't happen! The versions of the binaries in the installer don't each contain a copy of the help file; that would be extravagant. Instead, the installer itself writes a registry entry pointing at the proper help file, and the executables will look there. Another effect of this commit is that I've withdrawn support for the older .HLP format completely. It's now entirely outdated, and supporting it through this security fix would have been a huge pain. |
||
|---|---|---|
| .. | ||
| installer.wxs | ||
| msiplatform.py | ||
| pageant.ico | ||
| pageant.mft | ||
| pageant.rc | ||
| pageants.ico | ||
| plink.rc | ||
| pscp.ico | ||
| pscp.rc | ||
| psftp.rc | ||
| putty.ico | ||
| putty.iss | ||
| putty.mft | ||
| putty.rc | ||
| puttycfg.ico | ||
| puttygen.ico | ||
| puttygen.mft | ||
| puttygen.rc | ||
| puttyins.ico | ||
| puttytel.mft | ||
| puttytel.rc | ||
| rcstuff.h | ||
| README-msi.txt | ||
| README.txt | ||
| sizetip.c | ||
| version.rc2 | ||
| website.url | ||
| win_res.h | ||
| win_res.rc2 | ||
| wincapi.c | ||
| wincapi.h | ||
| wincfg.c | ||
| wincons.c | ||
| winctrls.c | ||
| windefs.c | ||
| windlg.c | ||
| window.c | ||
| wingss.c | ||
| winhandl.c | ||
| winhelp.c | ||
| winhelp.h | ||
| winhelp.rc2 | ||
| winhsock.c | ||
| winjump.c | ||
| winmisc.c | ||
| winmiscs.c | ||
| winnet.c | ||
| winnohlp.c | ||
| winnoise.c | ||
| winnojmp.c | ||
| winnpc.c | ||
| winnps.c | ||
| winpgen.c | ||
| winpgnt.c | ||
| winpgntc.c | ||
| winplink.c | ||
| winprint.c | ||
| winproxy.c | ||
| winsecur.c | ||
| winsecur.h | ||
| winser.c | ||
| winsftp.c | ||
| winshare.c | ||
| winstore.c | ||
| winstuff.h | ||
| wintime.c | ||
| winucs.c | ||
| winutils.c | ||
| winx11.c | ||
PuTTY README
============
This is the README file for the PuTTY installer distribution. If
you're reading this, you've probably just run our installer and
installed PuTTY on your system.
What should I do next?
----------------------
If you want to use PuTTY to connect to other computers, or use PSFTP
to transfer files, you should just be able to run them from the
Start menu.
If you want to use the command-line-only file transfer utility PSCP,
you will probably want to put the PuTTY installation directory on
your PATH. On Windows 7 and similar versions, you can do this at
Control Panel > System and Security > System > Advanced system
settings > Environment Variables.
Some versions of Windows will refuse to run HTML Help files (.CHM)
if they are installed on a network drive. If you have installed
PuTTY on a network drive, you might want to check that the help file
works properly. If not, see http://support.microsoft.com/kb/896054
for information on how to solve this problem.
What do I do if it doesn't work?
--------------------------------
The PuTTY home web site is
https://www.chiark.greenend.org.uk/~sgtatham/putty/
Here you will find our list of known bugs and pending feature
requests. If your problem is not listed in there, or in the FAQ, or
in the manuals, read the Feedback page to find out how to report
bugs to us. PLEASE read the Feedback page carefully: it is there to
save you time as well as us. Do not send us one-line bug reports
telling us `it doesn't work'.