[Maureen]

Changes in SecureCRT 5.0 (Alpha) -- July 7, 2004

New features:

• Open any session in a tab. To get a new tab session, map the Menu function MENU_TAB_NEW to a key using the Keymap Editor. Other related Menu functions that can be mapped are MENU_TAB_NEXT and MENU_TAB_PREV.
• Open an SFTP session for the current SSH2 session in a tab. To get a new SFTP tab session on the current SSH2 channel, map the Menu function MENU_TAB_SFTP to a key using the Keymap Editor.
• Share global settings between SecureCRT 5.0 and SecureFX 3.0.

Changes:

• 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 RemotePort property to the Session Script Object.
• 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.
• SSH2: Added support for diffie-hellman-group14-sha1 key exchange. The default order is as follows:
  
  1. diffie-hellman-group-exchange-sha1
  2. diffie-hellman-group14-sha1
  3. diffie-hellman-group1-sha1
• SSH2: Modified authentication UI so that more than two authentication methods can be specified.
• SSH2: Key exchange algorithm names are now case insensitive.
• SSH2: When the remote system offers a choice of host key types, RSA is preferred over DSA.
• SSH2: Improved the port forwarding trace output.

Bug fixes:

• Launching a Quick Connect session after launching a saved session created an ALL CAPS entry in the host key database.
• In tabbed sessions, SecureCRT always scrolled to bottom when a tab was activated.
• Launching SecureCRT from web browser did not work with the user@hostname syntax.
• SSH2: SecureCRT crashed when multiple tabbed sessions were connected to OpenSSH and the first tab was closed.
• VCP and VSH: When the password was specified on the command line, the password was prompted for anyway.