SecureCRT v6.5.8.380 汉化版

SecureCRT(R) 5.1.3 (Official) -- July 25, 2006 Copyright (C) 1995-2006 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 5.1.3 (Official) -- July 25, 2006 ------------------------------------------------------ Changes: - SSH1: Compression is now off by default. Bug fixes: - Reduced the time it takes for the Connect dialog to display, which was noticeable on a network or USB drive. - Running a script that modified the ANSI colors caused SecureCRT to crash. - When CTRL+TAB was used to switch between tabs, the scrollbar had the position of the most recently active tab rather than the previous position for that tab. - The keymap assignments changed when there were multiple tabs and a session in a tab other than the first tab was reset. - It was not possible to specify a UNC path (Samba) for a log file as it was in versions prior to 5.0. - In SecureCRT 5.1.2, it was not possible to disable "Send initial carriage return" in Logon Scripts as in previous versions. - SSH1: Under certain circumstances, SSH1 port forwarding ended abruptly. - SSH1: When generating an RSA key for an SSH1 session, if the user did not have write permissions for the specified save folder, SecureCRT crashed. - SSH1: The NO-OP anti-idle option caused random characters to be sent to Cisco ISR routers. The "Send protocol NO-OP" session option can now be turned off for SSH1 sessions. - SSH1: It was not possible to specify the DES cipher from the command line for SSH1 sessions. - VSFTP: If the "version" command was issued when VSFTP was not connected to a session, VSFTP crashed. Changes in SecureCRT 5.1.2 (Official) -- May 25, 2006 ----------------------------------------------------- Bug fixes: - Line drawing did not work correctly for SCO ANSI emulation. - When the default session was edited and a tab other than the first tab was active, the "Apply change to all sessions?" prompt was displayed even if no changes were made. - Under certain circumstances, the color change sequence for 256-color Xterm emulation was split between buffers, which caused some colors to be displayed incorrectly. - SSH2: SecureCRT could crash when using the TAB key to complete a filename in an SFTP tab, especially if TAB was pressed multiple times. Changes in SecureCRT 5.1.1 (Official) -- April 25, 2006 ------------------------------------------------------- Changes: - For new installations, the default local directory for SFTP tabs is now "My Documents". The SFTP local directory can be set through a session INI-file only option called "Sftp Tab Local Directory". Bug fixes: - There were problems with line drawing characters and menu positions when running dellmgr. - On 64-bit systems, pressing "8" brought SecureCRT to the foreground. - In some cases, when the SecureCRT window was maximized, the arrow control was placed in the tab bar even though it was not necessary. - SSH2: Under certain circumstances, SecureCRT crashed when attempting to start an X client using SSH2 X11 forwarding. - SSH2: The trailing slash was no longer being appended during local file completion. This was a change in behavior from 5.0. - SSH2: It was not possible to change the passphrase of a public key through the Public Key Properties dialog. - SSH2: When initiating an SSH2 password change from the Password Properties dialog and multiple authentications were selected, misleading errors were displayed. Changes in SecureCRT 5.1 (Official) -- March 28, 2006 ----------------------------------------------------- Bug fixes: - In some cases, escape sequences beginning with "ESC ]" were incorrectly interpreted. Changes in SecureCRT 5.1 (Beta 4) -- March 14, 2006 --------------------------------------------------- Changes: - Added Global.ini option "Serialize Connections". If this option is set, when multiple sessions are connected at the same time, they are connected serially instead of in parallel. - VCP/VSH: The command-line clients now display unsupported host-key algorithms as they are received from the server. Previously unsupported algorithms were displayed as blank strings. - VCP/VSH: Entering the wrong passphrase for an SSH1 RSA public key no longer displays an "invalid structure" error. Users are now prompted to enter a passphrase until they use the correct one or cancel. Bug fixes: - If a generic proxy was misconfigured, it caused SecureCRT to hang, and disconnecting the session caused SecureCRT to crash. - SecureCRT crashed when unsaving a password for a session and password that had been specified on the command line. - The tab status indicator changed to "connected" when connecting to a host that did not exist if another tab that was connected was selected before the connection attempt timed out. - SSH2: When editing the default session, it was possible do a password change. - SSH2: Under certain circumstances, even though an X.509 host key had been accepted and saved, SecureCRT asked about accepting it during key re-exchange or when reconnecting. Changes in SecureCRT 5.1 (Beta 3) -- March 2, 2006 -------------------------------------------------- Changes: - The installation program no longer removes old versions of SecureCRT from Windows Add/Remove Programs. - For DNS addresses, SecureCRT uses the return list as is, rather than preferring IPv4 addresses. Bug fixes: - If SecureCRT and SecureFX were integrated, but were out of sync, it was possible for the authentication method and key exchange lists to be empty on the SSH2 page in the Session Options dialog. - After installing SecureCRT for the first time, upon starting, the user was prompted to configure TAPI information and SecureCRT crashed if the dialog was cancelled. - Under certain circumstances, printing did not work after upgrading from a version of SecureCRT prior to 5.0. - If a log file name with parameter substitutions was specified and "Prompt for filename" was set, the log file name was not honored. - In the Quick Connect dialog, changes made to the default session were only reflected for the default protocol. - The transfer protocol name was modified in the session .ini file every time a connection attempt to that session was made. - SSH1: Under certain circumstances, authentication failed when connecting to an SSH1 server using Quick Connect. - SSH1: Entering the wrong passphrase for an SSH1 RSA public key resulted in an "invalid structure" error. - SSH2: In the Local Port Forwarding Properties dialog, it was not possible to use the same local port as another port forward when the local IP address was different. Changes in SecureCRT 5.1 (Beta 2) -- February 21, 2006 ------------------------------------------------------ New features: - Added history support to the chat window, allowing previous commands to be viewed, edited, and sent. - SSH2: Passwords for SSH2 sessions can be changed from the Session Options dialog using the SSH2 protocol when it is supported by the remote machine. Changes: - Added a global-file-only option "Clipboard Data Format", which allows the clipboard data format to be set to CF_TEXT, CF_OEMTEXT, o