SecureCRTchs

SecureCRT(R) 6.1.4 (Official) -- February 24, 2009 Copyright (C) 1995-2009 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 6.1.4 (Official) -- February 24, 2009 ---------------------------------------------------------- Bug fixes: - If a custom menu file that contained MENU_SCRIPT_MRU_FILE1 was used, selecting a script from the recently used script list could launch the wrong script. - If the "User Arranged Tree" option was set in the Connect dialog and sessions were rearranged, the changes were not saved. - If two sessions had different color schemes and a session was sent to a new window, and then a session was dragged into the other window, it had the first tabbed session's color scheme. - Selecting "Print Setup" from the File menu always displayed the printer settings for the first tabbed session. - RLogin: RLogin sessions could disconnect after a large amount of data was received. - SSH1/SSH2: An X11 forwarding request succeeded when it should have failed because a different user connected. Changes in SecureCRT 6.1.3 (Official) -- December 2, 2008 --------------------------------------------------------- Changes: - SSH2: The default cipher list has been modified to prefer the AES ciphers in CTR mode. This change was made to address a potential vulnerability. See the following web page for more information. http://www.vandyke.com/support/advisory/2008/12/cpni-957037.html Bug fixes: - SecureCRT could crash if the "Auto reconnect" option was set and the username was changed when attempting to connect to a server that does not allow the username to change. - If the INI-file-only global option "Disable Close" was set and SecureCRT was closed using the red "X", SecureCRT hung. - If a script was specified on the command line and the "Show connect dialog on startup" option was set, the Connect dialog was displayed. - If there was an error during script recording and the error message was longer than 64K, the message could not be displayed. Changes in SecureCRT 6.1.2 (Official) -- November 6, 2008 --------------------------------------------------------- Changes: - SSH2: In the session .INI file, if the GEX Preferred Size was set to 2046, it will be changed to 2048 in order to be compatible with Cisco IOS 12.4 or later. Bug fixes: - If a script was specified on the command line, SecureCRT was in a hung state after the script executed. - With ANSI color enabled, if a color escape sequence was received, only the portion of the row that contained characters was correctly displayed. - SSH2: In an SFTP tab, if the connection was lost and a put command was issued, SecureCRT crashed. Changes in SecureCRT 6.1.1 (Official) -- October 2, 2008 -------------------------------------------------------- Bug fixes: - If the auto-reconnect option was set for a session and the connection was lost, an error dialog was displayed. The 5.5 behavior of not displaying a dialog was restored. - If the session option "Display logon prompts in terminal window" was not set and a logon script was specified, the script was started before the connection was established. The 6.0 behavior of starting the script after the connection is established was restored. - Logon scripts were run when the administrative option to disallow scripts from being run in SecureCRT was set. - If the global option "Show confirm disconnect dialog" was set and multiple sessions were open in different windows, exiting the Activator could cause SecureCRT to crash. - SecureCRT crashed when cancelling out of the select log file dialog if the session tab no longer existed. - In the Connect dialog, doing a Find Next after deleting a session that had been found using Find caused SecureCRT to crash. - In the Global Options dialog, on the Firewall page, double- clicking the empty space below the firewall list or pressing the DEL key when no firewall was selected caused SecureCRT to crash. - After answering "No" to the confirm disconnect dialog, SecureCRT became unresponsive. - Under certain circumstances, if there were multiple SecureCRT windows and the menu bar was toggled, SecureCRT could become unresponsive. - After selecting text in the scrollback buffer using a triple- click, it was no longer possible to select text in the scrollback buffer. - If the SecureCRT window was maximized after scrolling up, garbage was displayed in the session window. - If an "exit" command was sent to a session in a script and then another connection was immediately attempted, it could cause the script to hang. - If a session was connected using the Session.Connect(/s <session>) scripting method, the initial position specified in the session options was not honored. - SSH2: The TCP connection associated with a dynamic port forward could get stuck in a CLOSE_WAIT state after the session was disconnected. - SSH2: Under certain circumstances, dynamic port forwarding was not started when a session was connected. - SSH1/SSH2: If the session option "Start log upon connect" was set and no log file was specified, when connecting to the session, after entering the password, focus went to the session window instead of the Select Log File dialog. - Global Secure Shell configuration information was not being migrated. - If two sessions had the same name, hostname, and username, they were combined during migration, but only the terminal protocol was set. Changes in SecureCRT 6.1 (Official) -- August 21, 2008 ------------------------------------------------------ Bug fixes: - Under certain circumstances, SecureCRT could not write log files to a mapped drive. - Under certain circumstances, when Quick Connect was used to make multiple connections, the authentication dialog was associated with the initial session window. - If nothing had previously been typed into the session window, pressing ALT+<numeral> sent the number to the session rather than switching to the specified tab. - When Windows was configured to use large fonts (120 DPI), some text in the Session Options dialog did not fit in the dialog. - If a URL that spanned multiple lines had extra spaces at the end of a line, the extra spaces were not removed when the URL was opened. - Serial: After a serial session was disconnected, the tab connec- tion status indicator was not updated to reflect that the session had been disconnected. Changes in SecureCRT 6.1 (Beta 4) -- July 31, 2008 -------------------------------------------------- Changes: - SSH2: Because of a limitation in some recent versions of Cisco's IOS which resulted in SecureCRT not being able to connect, the diffie-hellman-group-exchange key exchange algorithm was modified to send a different maximum size for the modulus. Bug fixes: - SecureCRT crashed when running a script that attempted to connect to multiple sessions. - Calling Config.GetOption("Password") in a script caused SecureCRT to crash. - After calling the script Session object method Connect, execution of the script continued regardless of whether or not authentication had completed. - When the global option "CTRL+TAB switches to mo