tinyurl.com/2rpub -> www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
These features are new in beta 055 (released 2004-08-03): * Security fix: a vulnerability discovered by Core Security Technologies (advisory number CORE-2004-0705), potentially allowing arbitrary code execution on the client by a malicious server before host key verification, has been fixed. These features were new in beta 054 (released 2004-02-12): * Port to Unix! These features were new in beta 053b (released 2002-11-12): * Fixed an embarrassing command-line bug: the -P option didn't work at all.
These features were new in beta 053 (released 2002-10-01): * The feature everyone's been asking for: ANSI printer support. Currently this sends data to the printer in completely raw mode, without benefit of Windows GDI or the printer driver; so it will be fine for anyone whose server already knows what type of printer it expects to be talking to, but probably not ideal for someone who wants to print a text file and have it look nice. A less raw mode of printer access is still on the Wishlist, but is quite a big piece of coding work so it's in the Implausible section.
The installer associates this file extension with Pageant and PuTTYgen. Basic password authentication is supported in SOCKS and HTTP proxies. Many thanks to Justin Bradford for doing most of the work here. Most of these options are ones that Plink has always supported; however, we also support a number of new options similar to the OpenSSH ones (-A and -a, -X and -x, and similar things; This feature is disabled if Pageant can't find the PuTTY binary on startup. These features were new in beta 052 (released 2002-01-14): * A full manual has been written, and is supplied as a Windows Help file alongside the program executables. com have a different agent protocol which they haven't published. credit mostly goes to Colin Plumb for letting me know about it. It will refuse to let the remote host write to a file that doesn't have the same name as the file that was requested. scp1's implementation of server-side wildcards is inherently unsafe. If you are sure you trust your scp server not to be malicious, you can use the "-unsafe" command line option to re-enable this behaviour. When using the new SFTP-based back end none of this is a problem, because SFTP is better designed. Thanks to Andreas Schultz for doing a large part of the coding for this. However, PuTTY does not currently attempt to authenticate connections to the local X server, because finding the authentication data to do so is server-dependent and complex and I thought I'd wait to see what servers people actually want to use this with. Not really like a DOS box, since it works within the current graphics mode rather than shifting into text mode, but it seems to work. Also supports a hybrid mode, in which window resizes change the terminal size but maximising or going full-screen changes the font size. In the first place this allows us to support servers which actually send UTF-8 down their terminal sessions; but the architecture changes also mean that instead of specifying the local and remote character sets in the Translation panel, you simply specify what character set you expect the server to be talking, and PuTTY handles the rest automatically. Note that this may fail because the rlogin protocol relies on TCP Urgent data, which not all operating systems get right, and which not all firewalls pass through correctly. Also, local flow control is unsupported as yet, and the "flush" command is not handled correctly. These are now separate options, controllable independently. PuTTY will make sensible guesses at the right settings, but those guesses can always be overridden by the user. you can choose a bell that plays the Windows default sound, or plays a sound of your choice, or flashes the window, or does nothing. In addition the window's Taskbar entry can be made to flash if a bell goes off when the window is minimised, and also there's an option that disables all bells if it receives them too fast (so that if you cat a binary file into your terminal it won't bleep for a week). Particularly useful for those of us using focus-follows-mouse, where the pointer is quite likely to be inside the window and obscuring the view. When it's a vertical line, it does something useful when not-quite-wrapping in the rightmost column. Also, you can make Pageant start another command once it's initialised itself; It should now be safe to use very large scrollback buffers without suffering noticeable slowdown. Compose behaviour on AltGr can still be configured on and off. If PuTTY is receiving data faster than it can send it out, it will attempt to slow down the entity it's receiving from rather than continuing to grow its buffers without bound. You should no longer see "Server failed host key check" after your session has been running for an hour. Crashes on network errors, bad handling of TCP Urgent data in telnet and rlogin, and truncation of output when the remote server sends a lot of data and then immediately closes the connection. These features were new in beta 051 (released 2000-12-14): * Addition of PuTTYgen, an RSA key generation utility. Since PuTTY uses the same RSA key file format as SSH 1, keys generated by PuTTYgen are usable with SSH 1 as well.
All errors are now translated into plain text: "Unexpected network error 10053" is a thing of the past. This should also have fixed random connection loss in Plink. Note: some of my experiments suggest that some SSH servers are not entirely happy with very large (80Kb or so) pastes, so if you still have problems, they may not be PuTTY's fault. This was causing chaos, as the rest of the code assumed it was there and so treated the first item in the list specially. These features were new in beta 050 (released 2000-10-16): * Keep-alives to prevent overzealous idle detectors in firewalls from closing connections down. Done by sending Telnet NOP or SSH_MSG_IGNORE, so as to avoid affecting the actual data stream. If you've used PuTTY on somebody else's machine and don't want to leave any mess behind, you can run this before deleting the PuTTY executable. Also, you can select items from the Event Log and copy them to the clipboard (should help for debugging). Now the behaviour is sane, and you can never open more than one About box. You can enter a public-key file name in the SSH configuration panel, and PuTTY will attempt to authenticate with that before falling back to passwords or TIS. PuTTY can use RSA keys from this for authentication, and can also forward agent communications to the remote end. Keys can be added and removed either locally or remotely. This is disabled by default unless you connect to a v2-only server. Public key authentication isn't supported (this places PuTTY technically in violation of the SSH 2 specification). With this feature, you can now set PuTTY as the default handler for Telnet URLs. exe %1" (with the full pathname of your PuTTY executable), you should find that clicking on telnet links in your web browser now runs PuTTY. PuTTY and PSCP now use the same protocol module, meaning that further SSH developments will be easily able to affect both. These features were new in beta 049 (released 2000-06-28): * Stop the SSH protocol code from sending zero-length SSH_CMSG_STDIN_DATA packets when Shift is pressed. These appear to be harmless to Unix sshd, but cause VMS sshd to generate an Exit signal.
An sshd with an 850-bit server key wasn't able to accept connections from PuTTY as a result. It does this by sending the command "ls -la <dirspec>", so it might well not work on non-Unix ssh servers. It's mainly there to allow a useful directory listing facility for potential GUI front ends. Now they don't get drawn at _all_, which is still non-ideal but it's better than rampaging screen corruption. The local line discipline can also be enabled and disabled in mid-session without dropping data, and it's also linked to the Telnet ECHO option. Q and CSI Q were treated identically for most values of Q Patch due to Robert de Bath. The DES, MD5, SHA, and CRC32 implementations used in PuTTY are now all written by me and distributable under the PuTTY licence, instead of being...
|
http://csua.com/feed/