SecureCRT(R) 5.0.5 (Official) -- February 14, 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.0.5 (Official) -- February 14, 2006 ---------------------------------------------------------- Changes: - SSH2: For GSSAPI authentication, the default SPN was changed from host@$(FQDN) to host@$(HOST) because DNS is not a secure system. Bug fixes: - SecureCRT crashed if the active tab was closed by clicking the close button or it was double-clicked and the double-click action for a tab was set to "Close". - SecureCRT crashed when closing a tab that had the "Close on disconnect" session option set. - If SecureCRT and SecureFX(R) were integrated and the "Reset All" button was pressed on the "File Types" page in the Global Options dialog, SecureCRT crashed. - Under certain circumstances, Zmodem downloads of files larger than 2 MB caused CPU usage to reach 100% and the transfer speed dropped significantly. - User handles were not being properly released, which could result in Windows running out of handles. - A buffer overflow was theoretically possible when a Unicode string was converted to a narrow string. - Serial: If multiple tabs were connected and a tab connected to a serial session was disconnected, when SecureCRT tried to reconnect to the serial session, it crashed. - SSH2: If GSS was supported by the server but not by the local machine and SecureFX tried to use a GSS key exchange method, it crashed. - SSH2: Using a PKCS#12 file for more than one session at a time could result in threading or synchronization problems. Changes in SecureCRT 5.0.4 (Official) -- November 10, 2005 ----------------------------------------------------------- Changes: - Added support for an execute escape sequence (eX&B) in Wyse emulations. - SSH2: When generating a public/private key, if the folder selected to write the key to does not exist, the Key Generation wizard now asks if it should be created. Bug fixes: - A C++ runtime error occurred when the log file was set to drive that was full. - When log data was supposed to be appended to an existing log file, it was being written to the top of the file. - If a session's character encoding was changed to OEM, the change did not take effect until SecureCRT was restarted. - If there were multiple monitors with different display resolutions, maximizing the SecureCRT window maximized to the size of the smaller display. - If the Activator was launched directly and SecureCRT was integrated with SecureFX, only recently used sessions from SecureFX were displayed. - In 5.0.2, if the remote machine disconnected, only the active tab's connection status indicator reflected the disconnected state. - Opening an SFTP tab or issuing an lcd command in a session changed the current directory for SecureCRT, which caused relative paths to be incorrect. - The escape sequence to set SecureCRT's title bar did not work with Wyse emulations. - Running SecureCRT and the Matrox Powerdesk application at the same time caused SecureCRT to crash. - SecureCRT could crash when closing a tab by double-clicking on it if that session was attempting to connect to a remote machine that was not responding. - SecureCRT crashed if the session was disconnected while a paste operation was in progress or if text was pasted into a disconnected session. - The file browse dialog changed the working directory, which affected how relative paths were interpreted in custom menu (.mnu) files. - Serial: Attempting to reconnect a disconnected serial tab caused SecureCRT to crash if there were multiple tabbed sessions. - Serial: Under certain circumstances, SecureCRT automatically connected to a session on startup even though an auto-session was not specified. - Telnet: Zmodem downloads of files 2 MB or larger caused the CPU to reach 100% and dropped the transfer speed to approximately 70 KB per second. - TAPI: If the line was busy, the "Disconnect" and "Reconnect" button states were not correct. - VSH: VSH created and used the SecureCRT 4.1 "Config Path" registry entry instead of the SecureCRT 5.0 entry. Changes in SecureCRT 5.0.3 (Official) -- September 8, 2005 ---------------------------------------------------------- Bug fixes: - Logging caused session output to be slow due to excessive disk access. - SecureCRT did not create a raw log or a session log unless the session option "Start log upon connect" was set. - Reconnecting to a tab after the session was renamed or deleted caused a crash. - Line drawing only worked correctly with the OEM character set when the Terminal font was used. - For Wyse emulation, the END key sent nothing instead of ^[T. - When switching between 80 and 132 columns, the number of rows was changed if a narrow font was used. - Under certain circumstances, if a script called the function "waitforstring" and then called the function "crt.screen.get", the string being waited for was found in the buffer, but the screen.get was coming from the window. - Under certain circumstances, it was not possible to open the Connect dialog from the Activator menu. - The title bar name specified on the command line using /TITLEBAR was not kept when switching between tabs. - The "Open in tab" check box was sometimes incorrectly set when using ALT+N or ALT+B to open sessions. - Version information was not included in trace output. - TAPI: When the line was busy, the "Disconnect" and "Reconnect" button states were incorrect. Changes in SecureCRT 5.0.2 (Official) -- August 11, 2005 -------------------------------------------------------- Bug fixes: - When the Activator was launched directly (e.g., from the Start menu or from a shortcut), only SecureFX's recently used sessions were shown. - Under certain circumstances, it was possible to get into a state where the last line of a session was not visible. - If the session option "Scroll to bottom on keypress" was set, the session did not scroll to the bottom when text was pasted. - In version 5.0.1, log files were missing carriage returns. - If a log file was specified from the File menu before connecting, SecureCRT did not log session I/O unless the session option "Start log upon connect" was set. - Calling the script function crt.session.disconnect caused the script to hang. - TAPI: If the connection was lost, the tab connection status indicator remained green. - SSH1: In the Session Options dialog, when TIS authentication was selected as the authentication method, the Properties button was enabled, but should have been disabled. - VSH: VSH sometimes crashed when remotely executing a command from the Windows Services for UNIX shell. - VCP: If the local path did not exist when a download was attempted, VCP did not fail. Changes in SecureCRT 5.0.1 (Official) -- July 14, 2005 ------------------------------------------------------ Changes: - Added the session name to the "Connection timed out" error message. Bug fixes: - At startup, SecureCRT was broadcasting a message that could cause the toolbar buttons in Outlook Express to expand. - If the "Close on disconnect" option was set and a cloned session was closed by clicking on the red "X" on the tab bar, SecureCRT crashed. - The product name was appended to the session title if the title was specified in the session options. - The "Always on Top" option did not work when a custom menu was used. - The command line was parsed incorrectly if a port ending in 1 or 2 was specified. - The script function crt.window.caption did not update the session tab. - When the global options "Show horizontal scrollbar" or "Show vertical scrollbar" were toggled, the window was not updated. - SecureCRT crashed if the transfer protocol was manually set to an invalid protocol and then edited in the Session Options dialog. - There was a missing comma in default.mnu. - SSH1: SecureCRT failed to connect to some SSH1 servers because SecureCRT sent an incorrect protocol version string. - SSH2: In the Public Key Properties dialog, an identity file could not be selected using the browse button. - SSH2: On the SSH2 page in the Global Options dialog, the public-key fingerprint was not updated when the identity file was changed. - SFTP: SecureCRT crashed when tab completion was attempted on a "mv" command. Changes in SecureCRT 5.0 (Official) -- June 16, 2005 ---------------------------------------------------- Bug fixes: - SSH2: In the Public Key Properties dialog, if the browse button was used to select an identity file for a session, the identity file field did not get updated. Changes in SecureCRT 5.0 (Beta 7) -- June 9, 2005 ------------------------------------------------- Changes: - Enhanced tab completion support in SFTP tabs. - If the completion is a directory, the trailing slash is appended. - If there are multiple matches, as much as possible is filled in. - New sessions created with the wizard use the hostname as the default session name. - Added support for deprecated GSSAPI authentication (-auth gssapi-deprecated) to the command-line clients VSH, VCP, VSFTP, and VPKA. Bug fixes: - SecureCRT crashed when running a script that connected to multiple hosts and one of the hosts was not available. - When the session option "Use ALT as meta key" was set, pressing ALT+ did not send the key to the remote application. - Piping output from "tar" command to Zmodem transferred a 0-byte file. - When the character encoding was set to "UTF-8", displaying high-bit characters caused the session to hang. - When SecureCRT and SecureFX were integrated, SecureCRT was newer than SecureFX, and the option to run the clients while temporarily not integrated was selected, the Transfer protocol was incorrectly shown in the Session Options dialog. - CTRL+C did not cancel transfers in SFTP tabs. - Commands that were typed in SFTP tabs during transfers were processed, which could result in strange behavior. - SecureCRT crashed if the file system filled up during a download from an SFTP tab. - Under Windows 98, when the command "ls -l" was typed in an SFTP tab, the file names and sizes were not displayed. - Under Windows 2003 and 98, the transfer progress was not displayed correctly in SFTP tabs. - TAPI: After disconnecting from a TAPI session and then attempting to reconnect, SecureCRT reported "Device is busy with another call". - SSH: In the Local Port Forwarding Properties dialog, if the "Dynamic forwarding using SOCKS 4 or 5" option was enabled, the remote Hostname and Port fields were still required. Changes in SecureCRT 5.0 (Beta 6) -- June 2, 2005 ------------------------------------------------- Changes: - Added the session name to disconnect/reconnect messages. - Improved handling of mismatched DLLs when SecureCRT and SecureFX are integrated. - SSH1: Added support for TIS authentication. - SSH2: Added new compatibility mode for Tectia using SHA1 hash with X.509 RSA certificates. Bug fixes: - SecureCRT sometimes took a long time to start or did not start at all. - Using ALT+ to navigate to a disconnected tab caused the status icon to change to connected. - The default keymap did not include the ALT+ keys. - SecureCRT sometimes displayed extra characters when Linux emulation and the Terminal font were used. - Line-drawing characters were not printed correctly although they were displayed correctly. - When SecureCRT could not load the default printer settings, it was not possible to exit the Printing pages in the Global and Session Options dialogs. - Under certain circumstances, Find highlighted an extra character. - Typing an exit command in an SFTP tab during a transfer caused SecureCRT to crash. - Pressing CTRL plus any key during a Zmodem transfer interrupted the transfer. - SecureCRT crashed when attempting to exit the application during a Zmodem transfer. - When the global option "Save window state for each session" was enabled and SecureCRT was started using a shortcut that was set to run minimized, the SecureCRT window did not start minimized. - Copying a session to a different folder failed if that session name already existed in the folder. - The menu item File\Print\Selection was sometimes available when nothing was selected. - SecureCRT crashed when a key was mapped to clone the tab and that key was pressed, but cloning was not allowed for that session. - License errors were reported as "317 and 317". - When SecureCRT and SecureFX were integrated and a session was saved using the Quick Connect dialog, a protocol did not get set for the other application. - It was not possible to integrate SecureCRT 5.0 and SecureFX 3.0 on machines if they had never been installed. - When SecureCRT and SecureFX were integrated, sometimes the icons displayed in the File Types page in the Global Options dialog were incorrect. - Serial: SecureCRT crashed when data was attempted to be sent after the session sending data had been closed. - TAPI: SecureCRT crashed when attempting to connect to a TAPI session and no modem was present. - SSH: Because the SSH1 and SSH2 key exchange algorithms settings were incorrectly being shared, SecureCRT could report "no compatible key exchange method" when attempting to connect. - SSH: SSH URLs did not working correctly. - SSH: The View Host Key dialog did not scroll when the host key did not fit. - SSH1: Modified the identity string to be the same as 4.1. which was what some devices expected. - SSH1: SecureCRT disconnected during Zmodem downloads and reported the error "Invalid packet header". - SSH2: In some cases, X11 forwarding was very slow. - SSH2: SecureCRT hung if certificate authentication was selected, but there were no certificates in the CAPI store. - SSH2: Could not use the GSSAPI key exchange method when connecting to an IP address and other key exchange methods were also allowed. - SSH2: Attempting to use an invalid public key caused SecureCRT to crash. - SSH2: The system function SHGetFolderPathA was being imported incorrectly, which caused problems on Windows 98. - VSH: Attempting to commit large modified binary files in CVS caused VSH to hang. Changes in SecureCRT 5.0 (Beta 5) -- May 12, 2005 ------------------------------------------------- New features: - Added a Tab page to the Global Options dialog. This page allows the following tab-related settings to be configured: - Whether or not to show status indicators - Color and width of status indicators - Minimum width of tabs - Double-click action - Whether or not to prompt when closing multiple tabs - Support for direct tab navigation. ALT+1 through ALT+0 navigate to tab 1 through tab 10, respectively. Keymap support for direct tab navigation is also available using the menu functions MENU_TAB_1 through MENU_TAB_10. - Support for tab completion in SFTP tabs. - Added an SFTP Tab page to the Session options dialog. This page allows the initial local and remote directories to be specified. - Added session option "Shift forces local mouse operations", which causes mouse operations to be local rather than remote when the SHIFT key is down. This option is on by default. - SSH1: Support for passphrase caching. Changes: - Added "Clone Session" to the File menu. - Added "Reconnect" to the tab menu. - If ClearType is not available on the system, the global option "Use Clear Type to smooth edges of screen fonts" option is grayed out. - Port forwarding warnings are now displayed as trace output instead of being displayed in message boxes. - Certain warnings are now displayed as trace output instead of message boxes so that sessions can automatically reconnect when the auto-reconnect option is set. - When SecureCRT is integrated with SecureFX, menu item "Show Transfer Sessions" on the right-click menu in the Connect dialog allows the transfer sessions to be displayed or hidden. - When SecureCRT is integrated with SecureFX, the toolbar, menu bar, and status bar settings are now separate. - The Activator now separates recent terminal and transfer sessions. - SSH2: Added support for GSSAPI group exchange as documented in draft-ietf-secsh-gsskeyex-08.txt. Bug fixes: - Launching sessions from a web browser did not work for IP addresses. - If a script had not finished when a session was disconnected and the session was reconnected, the session was hung until the script was canceled. - The status bar did not show the mouse position when a selection was being made. - In the status bar, the current cipher was sometimes truncated. - Under some circumstances, a default session was incorrectly started when SecureCRT launched. - The status indicator went to "connected" even when a connection to the remote host could not be established. - Trace Options were not honored when a session was reconnected. - Session options were not updated when the Session Options dialog was opened from tab context menu. - Using a mapped key to rename a tab label (MENU_TAB_RENAME) did not change the tab label. - The title bar was not updated when an escape sequence to change the title bar text was sent from remote machine. - If "Close on disconnect" was set, no warning was displayed when attempting to connect to a session with a bad hostname. - When a Zmodem transfer was in progress, it was not possible to switch tabs. - After a Zmodem or Xmodem transfer, a cursor artifact was left on the screen. - The New Session wizard was not using the Default session's protocol. - SFTP tabs incorrectly inherited Emacs mode. - SSH1: When doing port forwarding, the connection would hang on some machines because an agent forwarding request was being sent. - SSH1: Sometimes tabs did not close when the close tab icon ("X") was pressed. - SSH1: The port number was not remembered for a new SSH1 session. - SSH1: SecureCRT crashed when the Public Key Assistant was launched. - SSH1: SecureCRT crashed when port forwarding was specified to a port that was not listening. - SSH1: SecureCRT crashed when attempting to connect to an SSH1 session and the SSH1 DLL was not available. - VSFTP: Verbose output was not displayed when -v was specified on the command line. Changes in SecureCRT 5.0 (Beta 4) -- April 20, 2005 --------------------------------------------------- New features: - Support for KOI8-R encoding. Changes: - VSH: When -pw or -passphrase is specified on the command line, password or public-key authentication is preferred, respectively. Bug fixes: - If the WinSock 2 DLL was not currently initialized, the migration wizard crashed. - Calling the script function WaitForString caused the session to hang. - Using ANSI color caused the script function WaitForStrings to fail. - When using a custom menu and toolbar, the correct bitmaps were not being used by the toolbar. - Fixed several issues related to using USB devices with the Serial protocol. - RLogin: When attempting to reconnect to an RLogin session that was not exited cleanly, an error that the address was already in use was reported. - SSH1: The SSH_MSG_IGNORE message was not being handled, which resulted in the session being disconnected and reporting the following error: "Received packet for invalid channel". - SSH1: When SSH2, but not SSH1, was selected during installation, SSH1 was available in the list of protocols. - SSH2: When only public-key authentication was specified in the Quick Connect dialog, a password was prompted for under certain circumstances. Changes in SecureCRT 5.0 (Beta 3) -- April 5, 2005 -------------------------------------------------- New features: - Support for IPv6. - Support for local dynamic application-level port forwarding, which is similar to OpenSSH's and PuTTY's -D option. SecureCRT allows the specification of the port and address to bind to. - Multiple sessions can be specified on the command line using the /S command-line option. - VSH: Added support for SSH1. - VSH: Added an option (-remote) to allow reverse port forwarding. Changes: - For encrypted data such as passwords and logon scripts, the encryption algorithm was changed from CAPI back to Blowfish or encoded. - Complete rewrite of the SSH1 implementation, which fixed several SSH1-related issues. See "Bug fixes" for information about specific SSH1 bugs that were fixed. - For connections that have the "Auto reconnect" option enabled, typing "exit" in the shell no longer causes the session to try to reconnect. - Added MENU_TAB_CLONE to the keymap menu functions, which allows a key to be mapped to clone a tab. - Added MENU_TAB_SECUREFX to the keymap menu functions, which allows a key to be mapped to launch SecureFX. - Added custom menu/toolbar item for "Show session tabs". - The width of the Emulation / Advanced "Terminal type" and "Display tab as" text boxes was increased. Bug fixes: - Under Windows 98, SecureCRT performed an illegal instruction on startup that caused SecureCRT to crash or the machine to hang. - SecureCRT sporadically crashed when switching between tabs. - The text selection came back after changing context in remote applications such as Mutt and MicroEMACS. - Sometimes text in tabbed sessions would get selected even though no selection had been made. - Telnet URL handling was not working. - For tabbed sessions displaying the status icons, using CTRL+TAB to switch to a different tab did not reset the activity icon. - For tabbed sessions, if "Log session" was selected for multiple tabs, only the last session was logged. - When the title bar was set via an escape sequence from the host, the entire title was shown in the tab when it should have been truncated. - Under certain circumstances, the session prompt was not displayed after reconnecting to a disconnected session. - SecureCRT failed silently if a session name was specified on the command line, but no terminal session protocol was specified. - Specifying /SCRIPT scriptname on the command line did not work. - Pressing CTRL+PRTSCN or ALT+PRTSCN caused the current SecureCRT screen to be printed. - Pressing CTRL+TAB while the left mouse button was down caused output to be suspended. - The script function crt.Window.Show did not work correctly. - Scripts that connected to multiple sessions did not work correctly. - It was not possible to reconnect to a Quick Connect session that had not been saved. - Disconnecting during a Zmodem transfer and then reconnecting caused a crash. - For Xmodem transfers, the option to send 1024-byte packets (Xmodem-1k) was not honored. - Clicking the "NumLock" check box in the Keymap Editor caused a crash. - After changing the active keymap to a newly created custom keymap, the session was not updated to use that keymap. - Under Windows XP, password characters were sometimes displayed as vertical bars instead of dots. - If the "Close on disconnect" session option was set for a session with a bad hostname and a connection attempt was made, SecureCRT closed without displaying a warning. - If a session was started minimized, resizing the session window did not take effect. - When smac or rmac were used, alternate characters were not displayed correctly. - When a tabbed session was edited from the Connect dialog, the changes were not used upon reconnecting. - SSH1: If an SSH1 session had the "Close on disconnect" option enabled, typing "exit" or CTRL+D caused SecureCRT to crash. - SSH1: Port forwarding sometimes caused 100% CPU utilization and stalling. - SSH1: Sessions were unable to connect through a SOCKS firewall. - SSH1: Sessions hung after connecting through a PIX firewall. - SSH2: SecureCRT could hang when using GSSAPI authentication. - SSH2: The reverse forward filter incorrectly filtered on the IP address of the server rather than on the IP address of the machine that originated the remote connection. - SSH2: Reconnecting to an SFTP tab did not work correctly. Changes in SecureCRT 5.0 (Beta 2) -- March 15, 2005 --------------------------------------------------- New features: - Added the ability to visually indicate whether a tab is connected, disconnected, or has received data. This can be toggled by editing the option "Show Session Tab Images" in the Global.ini file. Changes: - Modified SecureCRT to use the Windows common controls, which gives the user interface a more modern appearance. - Added "Disconnect" and "Session Options" to the tab menu. - A dialog is optionally displayed when a session that has different geometry settings is connected to in a tab subsequent to the first tab. Bug fixes: - Zmodem file transfers caused CPU usage to go to 100%. - It was possible for SecureCRT to get in a state where the full session area was not being used. - When the window was maximized, tabs subsequent to the first tab did not have the correct geometry. - The session window state was wrong when SecureCRT was run minimized. - Connecting from a script running in a tab other than the first tab caused a crash. - SecureCRT crashed when doing a Quick Connect if the default session specified a protocol that was not installed. - In SFTP tabs and VSFTP, wildcards were case sensitive when they should not have been. - The MENU_WINDOW commands in custom menus was not supported. - DNS resolution failed with hostnames that contained underscores. - Selecting "Connect Both" from the Connect dialog caused duplicate sessions to be added to the recently used session list. - The Wyse50 default keymap was missing the definition for the HOME key. - The SecureFX icon was grayed out when a version of SecureFX prior to 3.0 was installed. - When %U was used in the session option "Title bar", the username was not substituted. - After disconnecting from a session, ALT+ENTER reconnected the session rather than toggling full-screen mode. - The SSH2 protocol was not available under Windows NT 4. - When an SFTP tab was connected, the logon script was executed. - When the global options "Show horizontal scrollbar" or "Show vertical scrollbar" were toggled, the window was not updated. - For new installations, the initial window size was calculated incorrectly. - The migration wizard claimed it could not find any connection protocols in the SecureCRT 5.0 installation folder, even when they were there. - The migration wizard checked for a non-existent destination folder rather than an empty folder. Changes in SecureCRT 5.0 (Beta 1) -- March 1, 2005 -------------------------------------------------- New features: - Added support for tabbed sessions. Any session can be opened in a tab. Tabs can be rearranged using drag and drop. - Added ability to create an SFTP tab for the current SSH2 session. Line editing is supported. - Sessions can be cloned, which creates a new session identical to the current session. For SSH2, the transport is shared and re-authentication is not needed. For other protocols, authentication is required. - All settings can be shared between SecureCRT 5.0 and SecureFX® 3.0. When SecureFX is also installed, it is possible to launch SecureFX and connect to specific sessions from SecureCRT. This can be done from the tab menu or from the Connect dialog. The global and session options dialogs allow SecureFX settings to be modified from within SecureCRT when SecureFX is installed. - Added the ability to create multiple global firewalls, which can be used on a per-session basis. - Added support for 256-color Xterm. - It is now possible to apply changes made to the Default session to all sessions. Note that protocol-specific changes are only applied to sessions using that protocol. - Added a New Session wizard that can be used to create new sessions. - Added support for session descriptions. - Added support for Internationalized Domain Names (IDNs). - Added support for X Windows style window positions, where negative values specify the offset from the bottom or right. - Added the ability to map a key to "Send ASCII". - The following command-line tools were added to the installer. - VSFTP: An interactive command-line SFTP client. - VKEYGEN: A command-line tool for generating public keys. - VPKA: A command-line tool for uploading public keys. - Initial support for IPv6 has been added. Changes: - For encrypted data such as passwords and logon scripts, the encryption algorithm was changed from Blowfish to CAPI, which uses Microsoft cryptographic service providers to encrypt and decrypt data. - It is now possible to edit a disconnected session by selecting "Session Options" from the Options menu. - Added a menu item to clear the screen and scrollback at the same time. - In the MRU list, full folder names are shown instead of ellipses. - In the window title, the "not connected" label has been moved to after the session name. - Added beta forum link to the Help menu. - Added support for Wyse 60 screen swap. - In the Zmodem Upload dialog, added a mnemonic to the OK button. - A warning is now displayed when an invalid filename is entered as the log filename. - Added RemotePort property to the Session Script Object. - SSH2: For new installations of SecureCRT, the default cipher for SSH2 sessions is SHA1 instead of MD5. - SSH2: Added support for diffie-hellman-group14-sha1 key exchange. The default order is as follows: diffie-hellman-group-exchange-sha1 diffie-hellman-group14-sha1 diffie-hellman-group1-sha1 - SSH2: Modified authentication user interface so that more than two authentication methods can be specified. - SSH2: The keyboard-interactive prompt now includes the username and hostname. - SSH2: Key exchange algorithm names are now case insensitive. - SSH2: It is now possible to copy the challenge text from the keyboard-interactive authentication prompt to the clipboard. - SSH2: Improved the port forwarding trace output. - VCP/VSH: When "-i" is specified on the command line, public-key authentication is tried first. - VCP/VSH: Added an option (-accept_hostkey) to automatically accept the host key. - VSH: The options can now be specified in any order. - VSH: Added the following escape values: ~~, ~?, ~R, ~#, ~. - VCP: Added transfer progress indicator. Bug fixes: - In the Connect dialog, after pressing ENTER to expand a folder, pressing the first letter of a session to go to that session stopped working. - Launching SecureCRT from web browser did not work with the user@hostname syntax. - Sending a zero length file to SecureCRT using Zmodem caused a hang. - When the "Sessions" folder was renamed, all the configuration data was deleted. - Under some circumstances, the tooltip was not correctly displayed for custom toolbars. - SecureCRT appeared as a title bar only when the VT100 font was unable to be read. - Under some circumstances, SecureCRT displayed Finnish characters incorrectly using UTF-8 encoding. - Text with the blink attribute set was being redrawn unnecessarily when the "Enable blink" attribute was off for the color scheme, which caused flickering. - Calling WaitForStrings in a script prevented output from going to the screen. - SSH2: In the Connect and Quick Connect dialogs, if the hostname was blank and the "Upload" button was pressed, the upload failed. SecureCRT now prompts for the hostname. - SSH2: Launching a Quick Connect session after launching a saved session created an ALL CAPS entry in the host key database. - SSH2: Keys added through the agent did not preserve the filename/comment. - SSH2: The packet that X.509 signatures were being written to was not always large enough for the signature. - VCP/VSH: Keyboard-interactive authentication prompts were not displayed properly when multiple prompts were present or the prompts contained only informational text. - VSH: A license manager warning was displayed every time any CVS command was run. - VCP: Did not return an error code when SFTP access was denied. - VCP: Wildcards were case sensitive under Windows. - VCP: If file(s) to be uploaded were at the root level and the path specified on the command line included wildcards and drive information, the transfer failed.