SecureCRT® 4.0.9 (Official) -- October 16, 2003 Copyright © 1995-2003 VanDyke Software, Inc. All rights reserved. This file contains a SecureCRT product history. It includes lists of new features, changes, and bug fixes sorted by release. For a product description, installation notes, registration information, and contact information, please refer to Readme.txt (downloaded with this installation). Changes in SecureCRT 4.0.9 (Official) -- October 16, 2003 --------------------------------------------------------- Bug fixes: - Some printer drivers returned a null pointer as the printer port name, which caused SecureCRT to crash at start up. - Serial: SecureCRT sometimes disconnected when there was a serial error. Changes in SecureCRT 4.0.8 (Official) -- August 19, 2003 -------------------------------------------------------- Changes: - Added a global INI file-only option "EnableFontSmoothing" to specify whether or not ClearType fonts should be rendered as ClearType under Windows XP. Bug fixes: - In VT220 emulation, certain "non-printable" characters were being displayed as they would be for Linux emulation, which resulted in strange output when using a standard VT font. - In the Session Options dialog, leading spaces are now stripped from the Hostname field. - SecureCRT can now be associated with Telnet URLs. - After upgrading from SecureCRT 3.4, SecureCRT 4.0 was not finding the old configuration path location. Changes in SecureCRT 4.0.7 (Official) -- June 19, 2003 ------------------------------------------------------ Changes: - Under Windows XP, when a ClearType font is used as the session font, it is not rendered as a ClearType font so that the characters display correctly in the session window. - Changed the session printer font selection to allow both printer fonts and screen fonts. Bug fixes: - In Wyse 60 emulation, SecureCRT was clearing the PROTECTED state when it received character attribute escape sequences (e.g., DIM, BLINK, REVERSE). - If the option to add the command-line tools directory to the path was selected in the installer, the directory was added to the path multiple times on multiple installs. - If a session INI file from a SecureCRT installation prior to 3.4 was used and a keyboard emulation other than "Default" was used, the alternate keyboard emulation would be incorrectly unchecked on the session Emulation page. - In a custom menu, the STRINGTABLE entry for tooltip or status bar text could not be overridden for built-in commands. - SSH1: If the server did not support X11 forwarding, SecureCRT displayed the warning message "Server does not support X11 forwarding" and went into a loop that consumes the CPU. - SSH1: The key generation wizard defaulted to SecureCRT's installation folder instead of the user's application data folder. - SSH2: When attempting to port forward over OpenSSH 3.1p1, SecureCRT disconnected with the error "Received open confirmation for non-opening channel 0". Changes in SecureCRT 4.0.6 (Official) -- April 17, 2003 ------------------------------------------------------- Bug fixes: - SSH2: Running "ssh-add" on a remote host caused SecureCRT to crash after the passphrase was entered. - SSH2: If an incorrect passphrase was entered when connecting to an OpenSSH server, SecureCRT crashed. - With the Microsoft Hebrew or East Asian (CJKV) language packs installed, line-drawing characters were being incorrectly displayed. As a workaround, a session INI file-only option, "Use Unicode Line Drawing", was added. When this option is enabled, the current font's graphics characters are mapped to Unicode line-drawing characters. - Find did not correctly match some strings with repeated characters. For example, if the search string was "abc", the string "abcc" would not be found. - Changes made to any of the printer settings in the "Print Setup" dialog were not saved. Changes in SecureCRT 4.0.5 (Official) -- April 3, 2003 ------------------------------------------------------ Changes: - Modified SSH1 to do blinding in order to protect against an RSA private key timing attack (CERT Advisory VU#997481). - Added a session INI file only option "Keyboard Char Send Delay" to delay each key entered. This is a workaround for some CISCO devices using SSH1 that report a "CRC Check Failed" error. - Added handlers for the Wyse 50 80/132 column switching escape sequences. - Added support for the Wyse 60 answerback request escape sequence. - The SecureCRT log file is now readable by other Windows applications while SecureCRT is running. Bug fixes: - The "Use global public key setting" in the Public Key Properties dialog was ignored if the "Use certificate" session option had been previously saved. - Attempting to open several connections to the same SecureCRT session with a logon script defined resulted in an error. - In Wyse 50/60 emulation, when clearing unprotected characters with paces or other characters, protected characters were not being honored. - The Gssapi32.dll did not load properly. Changes in SecureCRT 4.0.4 (Official) -- February 20, 2003 ---------------------------------------------------------- Changes: - Transferring files using bulletin board Zmodem implementations caused CRC errors with implementations that did not understand DEL encoding. Added session option "Zmodem Encodes DEL". - VCP looks for a newline or carriage return character in order to determine if the ENTER key was pressed when authenticating. Bug fixes: - Sometimes selecting menu items, selecting text, or right-clicking to bring up a context menu did not do anything. - SecureCRT could crash when the Raw Log Session option was enabled and there was heavy network traffic. - SSH2: On Windows NT 4.0, sometimes certain keys did not work after authenticating. Changes in SecureCRT 4.0.3 (Official) -- January 21, 2003 --------------------------------------------------------- Changes: - Added support for 32-bit CRCs when performing Zmodem transfers. Bug fixes: - SecureCRT failed to scrub usernames, passwords, and passphrases from memory after use. Scrubbing memory prevents an attacker with access to memory or a memory dump from getting authentication information. - The "/pos" command-line option was not honoring negative pixel positions. - The Select Menu Toolbar File dialog was a Save dialog rather than an Open dialog, which resulted in SecureCRT trying to save the custom menu file rather than open it when selecting a custom menu file to use. - VSH was not correctly parsing full paths for the "Command" argument. Changes in SecureCRT 4.0.2 (Official) -- December 3, 2002 --------------------------------------------------------- Changes: - Changed the printer font selection to allow both printer fonts and screen fonts. This allows line drawing characters to be printed. Bug fixes: - SecureCRT would crash if the authentication type "none" succeeded. - On the command line, using the /LOCAL flag with /SSH2 did not establish the port forward specified. Changes in SecureCRT 4.0.1 (Official) -- November 7, 2002 --------------------------------------------------------- Features: - Ability to specify the authentication method when using VCP and VSH. - GSSAPI support in VCP and VSH. - Ability to specify passwords and passphrases on the command line to VSH. Changes: - Added support for UTF-8 output. RedHat 8.0 shipped with UTF-8 as their default output encoding and this caused problems with the display of some characters in SecureCRT. Bug fixes: - Using the SAM tool on HP-UX resulted in screen artifacts due to an emulation error related to the handling of the cursor position. - SecureCRT crashed on exit if "Close on disconnect" was turned on. - Wyse emulations failed to line wrap when using certain applications like vi. - VCP used STDOUT for interactive feedback, which caused problems when used with VShell in TTY mode. - When dumping binary output to a printer in raw mode over a Telnet connection, SecureCRT did not strip NULs after carriage returns. - When top and bottom margins were set, the wrong lines were added to the scrollback history. Changes in SecureCRT 4.0 (Official) -- October 8, 2002 ------------------------------------------------------ Bug fixes: - SSH2: 8-bit ASCII characters were being translated into UTF-8 when entered into the password or username dialog, preventing the user from logging onto the remote host. They are now sent as 8-bit ASCII when the remote host is not VShell. Changes in SecureCRT 4.0 (Beta 7) -- September 26, 2002 ------------------------------------------------------- Changes: - SSH2: The public-key assistant failure dialog now displays a more descriptive error message. Bug fixes: - SSH2: In the Local Port Forwarding Properties and Remote Port Forwarding Properties dialogs, if the Hostname field contained anything, it was always used for port forwarding. - Xmodem uploads caused SecureCRT to hang if the receiver failed to acknowledge the EOT. Changes in SecureCRT 4.0 (Beta 6) -- September 12, 2002 ------------------------------------------------------- New features: - Session and global options for configuring the serial port when using direct pass-through printing. - Support for multiple pages when using Wyse 60. - Support for printing when using Wyse 50/60. Changes: - Added support for passing empty strings to scripts when using the /ARG switch on the command line. Bug fixes: - SecureCRT had a resource leak that could result in the error "No fonts installed" being displayed after resizing the SecureCRT window. - SecureCRT could display blank dialogs or crash when using TAPI as the protocol. Changes in SecureCRT 4.0 (Beta 5) -- August 29, 2002 ---------------------------------------------------- Changes: - SSH2: Port forwarding is now allowed on same local port if the local IP address is different (i.e., 127.0.0.1:23 and 127.0.0.2:23). - Added "reverse" pass-through printing so that output can be captured from a COM port and passed through to a Telnet session. Bug fixes: - SSH2: SecureCRT crashed when the "Public-Key Assistant" button was pressed. - SSH2: SecureCRT could crash when the "disconnect" button was pressed if SecureCRT sent a response to a channel request after the channel close but before the remote side responded to the close. - If both the global option "Use auto session" and the session option "Close on disconnect" were set and the default session's host was not accepting connections, SecureCRT started and then immediately exited. - In Wyse 50/60 emulation, line drawing characters were displayed as spaces. Changes in SecureCRT 4.0 (Beta 4) -- August 13, 2002 ---------------------------------------------------- New features: - The License Wizard reads license information from the clipboard if that information is present. Changes: - The Zmodem upload list now allows the specified files to be transferred as ASCII. - Added a ZmodemUploadAscii scripting interface which causes the files in the Zmodem upload list be transferred as ASCII. - Modified the Keymap Editor to allow keys to be disabled. - Added support for line drawing in Wyse 50 emulation. - Wyse 50 emulation now supports the " ;" sequence. - SecureCRT's application icons now use the color red to indicate when the current session is not connected. Bug fixes: - SSH1: When attempting to connect to a bad host, an incorrect error was displayed. - Sometimes the current session options were not correctly saved when SecureCRT exited. Changes in SecureCRT 4.0 (Beta 3) -- July 25, 2002 -------------------------------------------------- Bug fixes: - SSH1: Fixed a buffer overflow which could occur if a server- specific identifier string was more than the specified 40 bytes long. This could result in a malicious SSH1 server executing arbitrary code. - Zmodem uploads hung when the user did not have read access to the file being uploaded. Changes in SecureCRT 4.0 (Beta 2) -- July 23, 2002 -------------------------------------------------- Changes: - VSH: VSH displays a usage message when -help or -? is entered on the command line. - SSH2: Blank banner messages are no longer displayed. - Handle the escape sequence " [ ? 1 i", which prints the current line. Bug fixes: - The built-in Wyse 50/60 keymaps mapped the CTRL keys and the function keys to the wrong values. - VCP: VCP would hang when connecting to a misconfigured OpenSSH server. - VSH: Typing CTRL+C at the password prompt caused VSH to crash. - SSH2: In the Public Key Properties dialog, Change Passphrase did not use the current contents of the file name field. - SSH1, Telnet and rlogin: Sessions could display an unformatted error. - Serial: DTR flow control should have defaulted to handshake when DSR flow was enabled. - If the Auto reconnect option was on, the session would reconnect after a manual disconnect. - Changed the default VT100 keymap from "VT100" to "Default". - When using SOCKS 5 with client authentication, an error dialog was infinitely displayed if the username or password were incorrect. - SecureCRT could hang when launching the Opera web browser. - Administrative options were ignored if they were in the old registry location. - Fixed a highlighting problem in Wyse 50 emulation. Changes in SecureCRT 4.0 (Beta 1) -- July 2, 2002 ------------------------------------------------- New features: - SSH2: Public-key assistant. - SSH2: Command-line VSH utility. - VCP: Command-line option to suppress all prompts. - Basic Wyse 50/60 emulation. - Customizable toolbar and menu bar support. - Minimal character set mapping (character sets supported include: EUC-JP). - Selecting and printing of multi-byte characters is now supported. - The /ARG command-line option added to support passing arguments to scripts. - The Sleep() scripting function is now supported. - Improved support for the JAWS screen reader. - Added Most Recently Used Sessions list to Activator menu. - New improved Zmodem transfer dialog. - Config file-only support has been added to configure serial pass-through printers. Changes: - SSH2: Allows binding to an alternative local IP address (e.g., 127.0.0.2). - SSH2: Allows local port-forwarding to bind to ports on any 127.0.0.* address instead of just 127.0.0.1. - SSH2: SecureCRT now supports OpenSSH's ClientAliveInterval and ClientAliveCountMax. - SSH2: Improved support for keyboard-interactive authentication. - SSH2: To improve compatibility, SecureCRT now sends 38400 as the baud rate when requesting a PTY. - To improve compatibility, Xmodem now defaults to packets of 128 bytes. - Added mappings for SHIFT+PGUP and SHIFT+PGDN to Linux keymap. - Restored pre-3.4 ability to set logical and physical window sizes independently. - ANSI emulation now handles ENQ. Bug fixes: - SSH2: SecureCRT failed to send a failure response for unrecognized session channel requests. - Serial: A number of minor bug fixes related to DTR/DTS handling. - Auto reconnect would continue after receiving a Windows shutdown command. - Attempts to underline text by overprinting during pass-through printing failed to show other than the last character output to each character position. - A terminal reset would not clear VT_HOLD_SCREEN. - Changing the keyboard emulation could result in the path of the custom keymap file being blanked. - A crash could occur when CTRL+C was entered in an unconnected window. - A script that calls Disconnect() followed by an immediate call to Connect() could cause SecureCRT to crash.