These protocols are all used to run a remote session on a computer, over a network. PuTTY implements the end of the client for this session: the end at which the session is displayed, rather than the end at which it is executed.
In very simple terms: You run PuTTY on a Windows machine and tell it to connect (for example) to a Unix machine. PuTTY opens a window. Then everything you type in this window is sent directly to the Unix machine, and everything the Unix machine returns is displayed in the window. So you can work on the Unix machine as if you were sitting at his console while sitting elsewhere.
What's New:
- Security Patch: Preventing an infamous SSH server or network attacker from overwriting PuTTY at startup in three different ways by presenting a public key and a maliciously crafted signature.
- Security Patch: PuTTY no longer accidentally keeps the private half of users' keys in memory after being authenticated to them.
- Reorganization of the internal configuration storage system to remove any arbitrary limits set on the string lengths. In particular, there should no longer be an unreasonable limit to the number of port forwarding PuTTY can store.
- Port-redirected TCP connections that close one before the other should now be reliably supported, EOF being propagated independently in both directions. This also fixes some instances of port forwarding data corruption (if the corruption involved losing data at the end of the connection) and some instances of PuTTY did not close when the session was terminated (because it mistakenly thought that a transfer channel was still active when that was not the case).
- Terminal emulation now supports xterm parentheses pasting mode (allowing conscious applications to differentiate between typed text and pasted text, so publishers do not have to no need to apply inappropriate automatic indentation).
- You can now choose to display bold text by brightening the foreground color and changing the font, not just one or the other.
- PuTTYgen will never generate a 2047 bit key when asked for 2048 (or more generally n-1 bits when asked n).
- Some updates to the default settings: PuTTYgen now generates default 2048-bit keys (rather than 1024), and PuTTY uses default UTF-8 encoding and 2000 scrolling lines (rather than ISO 8859-1 and 200). ]
- Unix: PSCP and PSFTP now retain Unix file permissions on two-way copies.
- Unix: Dead keys and composition character sequences are now supported.
- Unix: PuTTY and pterm now allow fonts to be replaced (where glyphs not present in the selected font are automatically populated from other fonts on the system) even if you are using a server-side X11 font rather than A Pango client one.
- Fixed too many bugs to be listed, resulting primarily from code execution via Coverity Scan that detected an assortment of memory and resource leaks, logical errors, and crashes in various circumstances.
Legal Notice: The use of PuTTY, PSCP, PSFTP and Plink is illegal in countries where encryption is prohibited. I believe that it is legal to use PuTTY, PSCP, PSFTP and Plink in England and Wales and in many other countries, but I am not a lawyer and in case of doubt, you should seek the advice of a lawyer before downloading it. You can find this site useful (it's an investigation into the laws of cryptography in many countries) but I can not guarantee its accuracy.
The use of Telnet only binary (PuTTYtel) is subject to no restrictions by cryptographic laws.
[ad_2]
Source link