SecureCRT 5.0 alpha history
 

Changes in SecureCRT 5.0 (Alpha) -- June 3, 2004

New features:

• Added ability to specify that new sessions on the current SSH2 channel be displayed in tabbed windows. To get a new SSH2 session on the current SSH2 channel, map the SSH function SSH_NEW_SESSION to a key using the keymap editor. To enable tabbed sessions, select "Session Tabs" from the View menu. Other related SSH functions that can be mapped are SSH_NEXT_SESSION, SSH_PREV_SESSION, and SSH_CLOSE_SESSION.
• Added ability to create an SFTP tab for the current SSH2 session. To create an SFTP tab, map the Menu function MENU_TAB_NEW_SFTP to a key using the keymap editor. To enable tabbed sessions, select "Session Tabs" from the View menu. Other related Menu functions that can be mapped are MENU_TAB_NEW, MENU_TAB_NEXT, and MENU_TAB_PREV.
• VCP: Added transfer progress indicator.

Changes:

• 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.
• It is now possible to copy the challenge text from the keyboard-interactive authentication prompt to the clipboard.
• 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, ~#, ~.

Bug fixes:

• Calling WaitForStrings in a script prevented output from going to the screen.
• SSH2: Keys added through agent did not preserve the filename/comment.
• SSH2: The packet x.509 signatures were being written to was not always large enough for the signature.
• 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/VSH: Keyboard-interactive authentication prompts were not displayed properly when multiple prompts were present or the prompts contained only informational text.

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.

Have there been any updated builds recently?

I had hoped to make a new installer available last week, but there are a couple of bugs that need to get fixed first. I will make an installer available this week.

Maureen

Changes in SecureCRT 5.0 (Alpha) -- August 3, 2004

Changes:

• When SecureFX 3.0 is installed, the file transfer configuration pages are shown in the Global Options dialog.
• Added support for WYSE60 screen swap.
• Added the ability to map a key to Send ASCII.

Bug fixes:

• Send ASCII locked the keyboard for all tabs When multiple tabbed sessions were being used.
• VSH: If shell or remote execution were disabled on the remote machine, VSH hung when connecting.
• VSH: If the remote machine did not respond and immediatlely closed when trying to connect, VSH did not report an error.

Changes in SecureCRT 5.0 (Alpha) -- August 24, 2004

Changes:

• Added "New tab" and "New SFTP tab" to the File menu.
• Added a "New tab" button to the toolbar.
• Added a context menu for tabs.
• Modified Quick Connect dialog to allow connecting in a tab.
• 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.

Bug fixes:

• The menu function MENU_TAB_CLOSED disconnected a connected tab session instead of closing it.
• SecureCRT exited without prompting when the Close button was pressed, at least one session was connected, and the global option "Show confirm disconnect dialog" was set.
• Reconnect did not work correctly with tabbed sessions.
• When switching between tabs, some session options were not updated.
• Anti-idle strings did not work correctly with tabbed sessions.
• 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.

Changes in SecureCRT 5.0 (Alpha) -- September 3, 2004

Changes:

• SSH2: The keyboard interactive prompt now includes the username and hostname.

Bug fixes:

• Auto reconnect was not working correctly with tabbed sessions.
• Reconnecting a disconnected tabbed session caused a new tab to be created.
• If the only session was disconnected and a new session was connected, the window geometry was not correctly updated.
• SecureCRT crashed when the session configuration of a disconnected tab was modified.
• SecureCRT sometimes crashed when switching between tabs.
• ZModem output was not handled correctly for tabbed sessions.
• Trace output did not go the the correct window for tabbed sessions.
• When connecting to a new session in a tab, if the current tab had not connected yet, the current tab was used instead of creating a new tab.
• Selecting "Close" from the tab menu of a telnet or rlogin session disconnected the session instead of closing it.
• The disconnect prompt sometimes showed the wrong session name when disconnecting from a tabbed session.
• The tab label was not updated when the "Title bar" text was changed in the Session Options dialog.
• SSH2: The "locked" icon sometimes did not reflect the correct state for SFTP tabs.
• SSH2: Nothing happened when "New SFTP Tab" was selected from the tab menu of an SFTP tab.

Changes in SecureCRT 5.0 (Alpha) -- September 28, 2004

Changes:

• When a tabbed session is disconnected, the tab is closed if the session option "Close on disconnect" is set.
• Added an "Open in a tab" checkbox to the Connect dialog.
• Added alpha forum link to the Help menu.
• In the MRU list, full folder names are shown instead of ellipses.
• In the Global Options dialog, renamed the "Terminal Emulation" category to "Terminal.

Bug fixes:

• Could not connect when a generic proxy was used.
• The emulation setting was being reset to VT100 every time SecureCRT was restarted.
• When a sessions folder was renamed, all the configuration data was deleted.
• Autoreconnect happened for the active session, regardless which session had lost the connection.
• The Autoreconnect dialog did not say which session was being reconnected.
• The default firewall was SOCKS version 4 instead of None.
• The UI treated disconnected SSH1, serial, and TAPI sessions as though they were still connected.
• Reconnect did not work for SFTP sessions.
• Selecting "New SFTP Tab" from the tab context menu used the currently active tab rather than the tab that was clicked on.
• SecureCRT crashed if the SSH2 protocol was not installed.
• SSH1: When command-line arguments were specified for an SSH1 session, the port was reset to 22 and the authentication method was reset to password.
• VCP: Wildcards were case sensitive under Windows.

Changes in SecureCRT 5.0 (Alpha) -- September 30, 2004

Changes:

• When installing under Windows 95, the installer checks for the Winsock 2 DLL, which is now required.

Bug fixes:

• When a non-SSH2 session was edited or connected to, it was converted to an SSH2 session.
• SecureCRT crashed when the serial protocol was selected in the Session Options dialog.

Changes in SecureCRT 5.0 (Alpha) -- October 18, 2004

New features:

• Added support for 256-color xterm.

Changes:

• The Session Options dialog has been reorganized and shows session options for SecureFX if it is installed.
• The Connect dialog's "Open in tab" setting is used when opening a session from the MRU list.
• The preferred hostkey type has been changed back to DSA.

Bug fixes:

• Editing a session's properties after changing the protocol without saving the session caused SecureCRT to crash.
• Attempting to make an SSH2 connection to a non-SSH host caused the session to hang.
• SecureCRT crashed when attempting an SSH1 connection using a bad hostname.
• SecureCRT crashed when disconnecting from an SSH2 or SFTP session where a firewall was required but not used.
• Nothing happened when "New SFTP tab" was selected from the tab menu of an SFTP session.
• After closing an SSH2 tab and its SFTP tab, connecting to any SSH2 session opened an SFTP session.
• When attempting to lcd into the root of a drive in an SFTP tab, SecureCRT reported that the system could not find the file specified.
• The tab bar placeholder did not go away until the SecureCRT window was redrawn.
• SecureCRT crashed if a TAPI connection did not succeed.
• The phone number was not being saved for TAPI sessions.
• 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.
• Sometimes there were window redraw and size problems when the chat window was opened and SecureCRT was not connected to a session.
• WYSE50 emulation did not clear the screen when vi started.
• There was some strange behavior with selected text in vi.
• SFTP sessions could not retrieve the error text for errors.
• The Custom menu and toolbar file was not being displayed in the Global Options dialog.

Changes in SecureCRT 5.0 (Alpha) -- October 29, 2004

Changes:

• Added "Move right" and "Move left" to the tab context menu, which allows tabbed sessions to be rearranged.
• Added a close button to the tab bar.
• For new installations of SecureCRT, the default cipher for SSH2 sessions is SHA1 instead of MD5.
• In the window title, the "not connected" label has been moved after the session name.
• The "Session Tabs" menu item is always available.

Bug fixes:

• The screen was not always cleared when reconnecting to a session.
• The cursor was still shown after a session was disconnected.
• Sessions opened in subsequent tabs were not added to SecureCRT's recently used list.
• When SecureCRT was launched from the Start menu, the local path in an SFTP session was displayed using 8.3 format instead of long file names.
• Issuing an lcd command with a trailing backslash in an SFTP session caused an error to be reported.
• With multiple SFTP sessions connected, issuing an lcd command in one of the sessions changed the local directory for all SFTP sessions.

Changes in SecureCRT 5.0 (Alpha) -- November 15, 2004

Changes:

• Added "Show Descriptions" to the Connect dialog's context menu.

Bug fixes:

• The full descriptions were not being shown in the Connect dialog hover text.
• SSH2: When an IP address was specified as the hostname, the KEXINIT packet was sent twice, which caused the session to be disconnected.
• SSH2: The global option "Enable deprecated GSSAPI" was not being honored.
• SSH2: When a session with a saved password was copied and pasted, the password was incorrect.
• SSH2: In the Quick Connect dialog, uploading a public key failed when the hostname was blank. SecureCRT now prompts for the hostname.
• TAPI: When an attempt to connect to a TAPI session failed, SecureCRT crashed.

Changes in SecureCRT 5.0 (Alpha) -- November 30, 2004

New features:

• Added the ability to create multiple global firewalls, which can be used on a per-session basis.

Changes:

• 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 SSH1 public key can now be specified from the Session Options dialog on the Public Key Properties dialog.

Bug fixes:

• Sessions sometimes inherited the geometry from another window or a previous session.
• When a session was started minimized, the geometry was incorrect, which resulted in lines being cut off.
• If anti-idle was turned off for any session, the timer was turned off, which affected all sessions.
• When SecureFX was also installed, the file transfer protocol defaulted to SFTP, which resulted in an invalid combination for terminal protocols other than SSH2.
• When trying to create a new session, if the session name "New" already existed, an error was sometimes displayed as soon as the Session Options dialog was launched.
• Telnet: If a connection timed out or got a "reset by peer" error, SecureCRT crashed.

Changes in SecureCRT 5.0 (Alpha) -- December 14, 2004

New features:

• 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.

Changes:

• Only licenses issued on or after 12/1/03 are valid. Otherwise, an evaluation license will be generated.
• Renamed the menu item "New Tab" to "Connect in Tab" and the menu item "New SFTP Tab" to "Connect SFTP in Tab".
• If a connection is closed in a tabbed session that isn't active, the system will beep and the disconnected session's tab will flash.
• The "Auto reconnect" session option was moved to the Terminal page.
• When SecureFX is also installed, more protocol combinations are allowed.
• VCP/VSH: When "-i" is specified on the command line, public-key authentication is tried first.
• SFTP: When an SFTP tab is started, it is now positioned to the right of its parent session instead of to the far right.

Changes in SecureCRT 5.0 (Alpha) -- December 22, 2004

Changes:

• The Activator shows tabbed sessions in the session list.
• VSFTP: The usage message is displayed when /? is typed on the command line.

Bug fixes:

• Current session settings were not used when changes were made to a session that had been connected and was not the first tab.
• Cancelling a Zmodem transfer by pressing Ctrl+C caused print dialogs to be displayed when using WYSE50 emulation.
• The encoding was not preserved when pasting Unicode (UTF-8) data into a session.
• Under some circumstances, the tooltip was not correctly displayed for custom toolbars.
• Memory was leaked when there was a disconnected SFTP tab and SecureCRT was shut down.