mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-10 01:48:00 +00:00
91cf47dd0d
If Plink's standard output and/or standard error points at a Windows console or a Unix tty device, and if Plink was not configured to request a remote pty (and hence to send a terminal-type string), then we apply the new control-character stripping facility. The idea is to be a mild defence against malicious remote processes sending confusing escape sequences through the standard error channel when Plink is being used as a transport for something like git: it's OK to have actual sensible error messages come back from the server, but when you run a git command, you didn't really intend to give the remote server the implicit licence to write _all over_ your local terminal display. At the same time, in that scenario, the standard _output_ of Plink is left completely alone, on the grounds that git will be expecting it to be 8-bit clean. (And Plink can tell that because it's redirected away from the console.) For interactive login sessions using Plink, this behaviour is disabled, on the grounds that once you've sent a terminal-type string it's assumed that you were _expecting_ the server to use it to know what escape sequences to send to you. So it should be transparent for all the use cases I've so far thought of. But in case it's not, there's a family of new command-line options like -no-sanitise-stdout and -sanitise-stderr that you can use to forcibly override the autodetection of whether to do it. This all applies the same way to both Unix and Windows Plink. |
||
|---|---|---|
| .. | ||
| 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 | ||
| winhsock.c | ||
| winjump.c | ||
| winmisc.c | ||
| winmiscs.c | ||
| winnet.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'.