SecureCRTPortable.rar

SecureCRT(R) 7.0.3 (Official) -- January 17, 2013 Copyright (C) 1995-2013 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 7.0.3 (Official) -- January 17, 2013 --------------------------------------------------------- Bug fixes: - In the Connect dialog, if a folder was renamed to a string that ended in one or more "." characters, the sessions in the folder were deleted. - Opening the default session in a script caused SecureCRT to crash. - If the "Automate logon" items for a session were re-ordered, the changes were not saved. - If "/Serial" or "/Tapi" (Windows only) was specified on the command line, it was not honored. - If a session that contained ANSI color text in the scrollback was disconnected and reconnected, the ANSI color attributes were no longer in the scrollback. - When enough tabs were open to require the scroll control on the tab bar, if the right-most tab was activated and renamed, the tab bar shifted to the left and the active tab was no longer visible. - Serial: The stop bits were not logged correctly in the trace output. - SSH1/SSH2: If a session used a dynamic tunnel on port 10080 and another SSH1/SSH2 session went through the first session's SOCKS proxy and used a dynamic tunnel on port 1080, SecureCRT crashed when data went through the second tunnel. - Windows: When switching between tiled and tabbed sessions in a maximized window, the terminal area was 24x80 instead of the full window area. - Windows: If the global option "Minimize to Activator in system tray" was set and SecureCRT was closed, if "Connect" was selected from the Activator menu, the icons in the Connect dialog were not mapped to the correct actions. - Mac: The session option "Use ALT as meta key" was not always honored. - Mac: If the global option "Host key database location" was changed to a different path, the new path was not saved. - Mac: If a session prompted for a log file, after the file location was selected, focus did not return to the SecureCRT window. Changes in SecureCRT 7.0.2 (Official) -- October 25, 2012 --------------------------------------------------------- Changes: - Mac: The look of text on Retina displays was improved. - Linux: Character encodings that cannot be used by SecureCRT are no longer shown in Terminal/Appearance category in the Session Options dialog. Bug fixes: - If the protocol type was changed during authentication, SecureCRT crashed. - If a session's emulation was set to "Dumb", it continued to used dumb emulation after being changed to use a different emulation. - If a session reconnected automatically in the background when a different session's tab had focus, the title bar was updated to display the reconnected session name. - Windows: If a laptop was docked such that a secondary monitor was used and then SecureCRT was moved to that monitor and closed, when the laptop was disconnected from the dock and SecureCRT was restarted, it was visible in the task bar, but not on the laptop display. - Windows: On a system that had two monitors with the primary monitor having a larger display resolution than the secondary monitor, when SecureCRT was maximized on the primary monitor and then restored, it used the resolution of the secondary monitor. - Windows: When the sessions were tiled, if the main window was resized, some of the tiled windows did not send a screen resize to the remote system. - Mac/Linux: SecureCRT crashed after the Report button was pressed in the crash handler dialog. - Mac/Linux: If data was being output and the scrollbar was used to look at data in the scrollback buffer, the output was not paused. - Mac: Passwords specified on the command line were ignored if the global option "Use Keychain" was set. - Mac: If the global option "Show confirm disconnect dialog" was set and multiple SecureCRT windows with connected sessions were open and then one window was closed, attempting to switch between the remaining windows using COMMAND+` did not work. - Mac: When SecureCRT was not set as the default Telnet handler and the default Telnet handler check was on, a message was displayed every time SecureCRT went into or out of "Full Screen" mode. - Linux: Error text was not displayed correctly on Ubuntu with the Korean language pack installed and set as the primary language. Changes in SecureCRT 7.0.1 (Official) -- August 28, 2012 -------------------------------------------------------- Changes: - The xterm set title escape sequence ending with \033\\ is supported in addition to \007. Bug fixes: - If the username was sent to a session after the connection was gone, such as when the server had a short authentication timeout, SecureCRT crashed. - Hostkey database paths that contained "%USERPROFILE%" were not expanded correctly. - If a disconnected session had focus and other tabbed or tiled sessions were connected and the "Show confirm disconnect dialog" option was set, SecureCRT did not display the disconnect prompt when the application was closed. - Windows: SHIFT+INSERT could not be used to paste into the Connect bar. - When SecureCRT and SecureFX were integrated, if the configuration folder contained "%APPDATA%", attempting to launch SecureFX from the SecureCRT toolbar caused an error to be reported. - The ConnectInTab script function did not honor the "Reuse disconnected tabs" setting. - Windows: After maximizing and restoring a tiled session, the output was displayed in only the top half of the session window. - Windows: When a SecureCRT session was launched from the Windows 7 task bar "Connect..." menu item, it was displayed behind all other application windows. - Windows: A custom menu file configured in SecureCRT 6.7 did not take effect after installing version 7.0 until SecureCRT was closed and restarted. - Windows: When SecureCRT started in tabbed mode after switching between tabbed and tiled windows that connected sessions with small sizes, the application window was smaller than the specified session size. - Windows: When the Windows 7 task bar was not in the default location, and SecureCRT switched from tiled to tabbed mode, the tab bar was not in the correct location. - Windows: The New Session wizard allowed a session to be created with a name that was a Windows reserved keyword, such as COM1 or LPT1. - Mac: SecureCRT could not be installed on OS X 10.8 (Mountain Lion) without disabling the gatekeeper. - Mac: After creating a new or editing an existing color scheme, the Global Options dialog became unresponsive. - Mac: SecureCRT could hang when configuring the tab status indicator rectangle colors. - Mac: Pressing CTRL+TAB or CTRL+SHIFT+TAB did not switch to the next or previous tabs, respectively. - Mac: When SecureCRT was minimized to the dock, it could not be restored by left-clicking it. - Mac: On OS X 10.8 (Mountain Lion), SecureCRT could not locate crash dump files because they were being created in a different folder than in previous versions of OS X. - Mac: The title bar was displayed in full-screen mode. - Linux: SecureCRT prompted when the log file existed, although the "Append to file" op