SecureCRT 6.7.2 build 229绿色英文便携版

SecureCRT(R) 6.7.2 (Official) -- August 11, 2011 Copyright (C) 1995-2011 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.7.2 (Official) -- August 11, 2011 -------------------------------------------------------- New features: - Linux: Added support for Ubuntu 11.04. Changes: - Windows: The 32-bit installer can be installed on a 64-bit system. - Linux: Added an accelerator (ALT+M) to toggle the menu bar. Bug fixes: - Xmodem transfers failed over connections using the Raw protocol. - The hostname was not saved in sessions that used the Raw protocol. - The item MENU_GOTO_CONNECT_BAR did not work when it was mapped to a button on the button bar. - The Connect dialog allowed connect attempts to sessions with the protocol set to "None". - The extend evaluation feature did not work correctly. After the offer was accepted, there was no button to extend the evaluation on the "Enter License" dialog as described in the instructions that had been e-mailed. - Telnet/RLogin: On Windows 7, when multiple sessions were running in different windows such that they were separate processes and command output was streaming in them, one or more of the connections could get reset. - Windows: On 64-bit machines, if the menu or toolbar was customized in SecureCRT 6.0 and then version 6.7 was run and "Yes" was selected after the prompt "Would you like to update the toolbar and menu bar?" was displayed, SecureCRT crashed when it was closed. - Windows: When the SecureCRT window was restored after being maximized or in full screen mode, it was restored to the wrong size. - Mac: If the system language was set to Russian, SecureCRT crashed when it was launched. - Mac: Mapping a button on the button bar to launch an application did not work. - Mac: After going into full screen mode and connecting to another session, the last line of the new session was cut off. - Mac: The "Public Key Wizard" dialog was taller than necessary. - Mac/Linux: It was not possible to double-click a port forward item in order to open its "Properties" dialog. - Linux: Opening URLs did not work. - Linux: On Ubuntu, attempting to register SecureCRT by pressing the "Enter License Data" button on the dialog that appeared after the evaluation license expired did not work. Changes in SecureCRT 6.7.1 (Official) -- June 16, 2011 ------------------------------------------------------ Changes: - Mac: When GSSAPI authentication is specified for a session, SecureCRT now looks for "libgssapi_krb5.dylib" in addition to "libgssapi.so". Bug fixes: - If buttons were added to a new button bar and then an attempt was made to switch to a different button bar, SecureCRT could crash. - When Ymodem was used to transfer multiple files, only the first file was transferred correctly and sometimes the error "Invalid access to memory location" occurred. - In the Quick Connect dialog, if the port number was changed to something other than the default, the port number was reset to the default the next time the Quick Connect dialog was opened. - Windows: If a USB serial adapter was removed while the serial session was connected, SecureCRT could crash. - Windows: When the Windows 7 Areo snap feature was enabled, if the SecureCRT window was dragged so that it snapped to the side of the desktop and focus was switched to another application, when SecureCRT was restored from the taskbar, it reverted to its previous size. - Windows: If the Windows 7 Aero snap feature was enabled and SecureCRT was dragged by the title bar so that it was maximized using the snap feature, the SecureCRT window was partially off screen. - Mac: If the global option "Confirm when closing multiple tabs" was set and the "Do you wish to connect from all sessions?" prompt was displayed, SecureCRT closed even when "No" was selected. - Linux: On older processors, such as Pentium 4 or Pentium M, SecureCRT crashed when attempting to connect to a Secure Shell server. Changes in SecureCRT 6.7 (Official) -- May 26, 2011 --------------------------------------------------- Bug fixes: - The SHIFT+INS paste accelerator did not work when a custom menu (.MNU) was being used. Changes in SecureCRT 6.7 (Beta 5) -- May 17, 2011 ------------------------------------------------- Bug fixes: - If "/POS" was the only option specified on the command line, SecureCRT attempted to use the last argument as the remote host. - If the SecureCRT window was resized and trace options were on, the event was traced. Changes in SecureCRT 6.7 (Beta 4) -- May 3, 2011 ------------------------------------------------ Bug fixes: - SecureCRT could crash on exit due to the way threads were being cleaned up. - SecureCRT crashed if a session with the "Auto reconnect" and "Close on disconnect" options enabled was disconnected. - SecureCRT crashed after pressing OK on the "Session Options", "Lock Session", or "Confirm Disconnect" dialog if the session that launched it had been closed after the dialog was displayed. - SecureCRT crashed after pressing OK on a script dialog if the session that launched the script had been closed after the dialog was displayed. - When the /F parameter was used on the command line to specify the location of the configuration folder and the menu or toolbar was customized, the changes were not saved. - A pop-up error message was displayed if the script method GetOption() was called with an unknown option name. - Serial: After connecting to a Windows COM port and then pressing any key, the CPU was pegged. - SSH2/SSH1: When a session established a port forward that launched an application, if the session attempted to connect using both an IPv4 and IPv6 address, two instances of the application were launched. - Windows: On Windows XP, if the display theme was set to Blue, Black, Aqua, or Silver and more than one SecureCRT window was connected to a session and "Send chat to all tabs" was used to send text to one of the sessions, it caused the other window to freeze. - Mac: If SecureCRT was run on a Mac system with the keyboard and mouse being controlled from another system running Synergy in server mode, the arrow keys did not work. - Mac: In the "Connect" dialog, the search string from the "Find Session" dialog was not remembered for subsequent searches. Changes in SecureCRT 6.7 (Beta 3) -- April 12, 2011 --------------------------------------------------- Bug fixes: - If the Connect bar was removed from the toolbar through customization and then SecureCRT was restarted, attempting to bring up the customization dialog caused SecureCRT to crash. - If a script that called Crt.Screen.Send() was repeatedly run, it could cause terminal corruption and possibly a crash. - Under certain circumstances, after editing the Default session and attempting to apply the changes to all sessions, SecureCRT hung. - Scripts that called Crt.Screen.Send() to send end of line characters had different behavior than they did prior to version 6.7. - After pressing the ALT key and then the ENTER key, SecureCRT attempted to connect to a host named "<ALT+R>". - When the SecureCRT window was resi