SECURECRT个人使用，免安装版本

SecureCRT(R) 7.3.6 (Official) -- December 1, 2015 Copyright (C) 1995-2015 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.3.6 (Official) -- December 1, 2015 --------------------------------------------------------- Bug fixes: - The New Session wizard reported an error when an IPv6 address was entered as the hostname. - If the option "Show command window" was modified for the active session from the Session Options dialog, it did not take effect until the session was closed and re-opened. - When first switching from tiled to tabbed sessions, the session option "Show command window" was not honored. - If the command window was turned off while SecureCRT was in tiled mode and the application window was maximized, the sessions were not re-tiled automatically. - When the global option "Default transfer type" was set to "Prompt for type," the option "Use this type for all files" was enabled. - SSH2: SecureCRT hung when attempting to connect to a session that used CAPI for public-key authentication if the personal store was empty. - Mac: SecureCRT crashed when attempting to do public-key authentication with a certificate in a format not supported by SecureCRT. - Mac: If a password for a session was saved in the OS X keychain and then the option to save to the keychain was turned off, when connecting to the session, the authentication prompt contained an incorrect password. - Mac: On OS X 10.11 (El Capitan), there were display issues with the San Francisco system font. Changes in SecureCRT 7.3.5 (Official) -- September 10, 2015 ----------------------------------------------------------- Bug fixes: - An error was reported if a host was specified on the command line using an IPv6 address. - If a key was mapped to a key on the number pad and NUM LOCK was on, the mapped key did not honor the NUM LOCK setting. - Mac: On Yosemite (OS X 10.10), SecureCRT crashed at startup if the global settings contained an invalid value for the application window position or size. - Mac: If the option to reuse tabs was set and a tabbed session was disconnected and then another session was connected from the Session Manager, focus did not move into the session. - Mac/Linux: If the toolbar was unchecked in the View menu, it was displayed the next time SecureCRT started. Changes in SecureCRT 7.3.4 (Official) -- June 16, 2015 ------------------------------------------------------ Bug fixes: - If a tabbed session was closed while a transfer operation in that session was in progress, SecureCRT crashed. - When SecureCRT and SecureFX were integrated, if the configuration passphrase was changed in one application while the other application was running, the sensitive data could have been encrypted incorrectly. - The personal data folder could not be merged with the configuration folder if the personal data folder contained any empty session folders. - When the Session Manager was in autohide mode and a session was connected, if a menu was activated using the keyboard and dismissed by pressing ESC, and then the keyboard accelerator to display the Session Manager was pressed, the Session Manager gained focus but remained hidden. - SSH2: SecureCRT could crash when a smart card was used for authentication. - Windows: On Windows 10, the last line of the terminal session was partially hidden by the bottom of the application window. - Windows: On Windows 10, moving the SecureCRT window caused it to get smaller. - Windows: On Windows 10, every time a tiled session was connected, it shrunk by one row and one column. - Windows: On Windows 10, if the session rows and columns were changed in the Session Options dialog, the view size was one row and one column less than the specified values. - Windows: PKCS11 authentication failed with FortiToken ePass2003. - Windows: CAPI authentication failed with the Fortinet FTK300 token. - Mac: Due to a change in OS X 10.10 (Yosemite), there can be more than one $PATH, which meant that the $PATH variable used by SecureCRT might not have contained the expected paths. - Mac: If there were multiple SecureCRT application windows, the keyboard accelerators COMMAND+I and COMMAND+M did not work unless the Session Manager was open in all the SecureCRT windows. - Mac: The SecureCRT version should not have been displayed in the title bar for official releases. - Mac/Linux: In the Manage Agent Keys dialog, if all keys were removed and then the Remove button was pressed again, SecureCRT crashed. - Mac/Linux: The Help contents, search, and glossary were not available. Changes in SecureCRT 7.3.3 (Official) -- March 31, 2015 ------------------------------------------------------- New features: - Previous versions of SecureCRT supported saving passwords and other sensitive data. In order to improve the security of this feature, SecureCRT now requires a passphrase to be created the first time version 7.3.3 runs. This passphrase will be used to encrypt and decrypt sensitive data stored in the session database, such as passwords and send/expect logon scripts. Bug fixes: - SecureCRT hung if logon actions were being edited for multiple sessions and one of the strings being replaced was blank. - The crash reporter dialog, which reports crashes for previous runs of SecureCRT, was being displayed after the SecureCRT window was displayed, which caused confusion about when the crash had occurred. - SSH1: If the "Auto reconnect" global option was set and a session that did not have the username and/or password saved got disconnected, if the user did not respond to the username or password prompts, multiple prompts were displayed until SecureCRT eventually crashed. Changes in SecureCRT 7.3.2 (Official) -- February 26, 2015 ---------------------------------------------------------- Changes: - The escape sequence ESC E (DECNEL, next line) is treated like a CR (or CRLF) so that the command on that line gets logged. - SSH2: When attempting to authenticate using a CAPI key or certificate with a smart card, if the card returns an error, SecureCRT attempts to continue authentication, which allows authentication to succeed with certain smart cards, such as GoldKey. Bug fixes: - SecureCRT crashed when attempting to run a Perl script using ActiveState ActivePerl 5.18 and 5.20. SecureCRT still cannot run the script. Switching ActivePerl 5.16 is recommended. - When the global option "Save window state for each session" was set and SecureCRT was in full-screen mode, if a local shell session was opened or a session was cloned, SecureCRT went out of full-screen mode. - If autohide was on for the session manager, the most recently opened session was not selected when the session manager was shown again. - If a keymap was modified through a script, it was not always reloaded. - When using the Connect dialog, if a session with saved credentials was connected by double clicking, extraneous text appeared in the session window before the prompt. - Telnet: When connected to a session with a character or line send delay specified, the delay was not honored when a script sent a string. - Windows: On W