SecureCRT Changelog

New in version 7.3

October 28th, 2014
  • Changes:
  • Mac: The keyboard shortcut COMMAND+N opens a new window when the main application window has focus as it did in version 7.2.
  • Bug fixes:
  • SecureCRT crashed when attempting display the information for an incorrectly formatted SSH host key.
  • Windows: Selecting the "Update Now" menu item did not reset the clock used to check for updates every 30 days.

New in version 7.2.6 (August 20th, 2014)

  • The Session Manager and Connect dialog scrollable area was not large enough to show all sessions after expanding a folder that contained several sessions.

New in version 7.2.5 (June 6th, 2014)

  • Changes:
  • Linux: Added support for opening in a new SecureCRT window to the Ubuntu Unity QuickList icon.
  • Bug fixes:
  • SecureCRT could crash when TAPI sessions were closed.
  • Arguments passed to logon scripts were retained and used by scripts launched from the button bar or a mapped key.
  • The Connect dialog did not have a horizontal scrollbar.
  • Mac/Linux: Some licenses that contained international characters were not seen as being valid.

New in version 7.2.4 (May 2nd, 2014)

  • Changes:
  • In the Session Options dialog, the width of the Firewall dropdown was increased in order to accommodate long names.
  • Bug fixes:
  • When SecureCRT was installed on a machine where it had never been installed, if a session was created using the Quick Connect dialog and then the "Use dockable session manager" option was set in the Global Options dialog, the next time SecureCRT started, the Connect dialog was displayed twice.
  • If a license was validated with an issue date that contained an en dash or em dash, SecureCRT crashed when the About box was displayed.
  • Mac: On OS X Mavericks (10.9), under certain conditions, the scrolling speed was slow.
  • Mac: On Mavericks (10.9), typing in a connected session could be slow when curses-based output was on the screen.
  • Mac/Linux: Sometimes clipboard text was pasted into multiple tabbed sessions.
  • Linux: If more than two sessions were connected and the Connect dialog was displayed and then dismissed, CTRL+TAB no longer switched focus between the tabbed sessions.

New in version 7.2.3 (April 2nd, 2014)

  • Windows: If the Quick Connect dialog was shown at startup and dismissed, clicking on the Session Manager button in the toolbar caused SecureCRT to crash.
  • If the global value of "Menu Toolbar File V2" specified a templated value, such as "${VDS_INSTALL_PATH}, SecureCRT crashed on startup.
  • When sessions were sorted using the option to arrange the tree logically, the sessions were not sorted correctly.
  • In the Quick Connect dialog, if options such as "Show quick connect on startup" or "Save session" were changed and then the dialog was cancelled, the options were saved.
  • If a new color scheme that had the same properties as an existing color scheme was created, it was not saved.
  • SSH2: When the /LOCAL parameter was specified on the command line, the port forward was not established.
  • SSH2: When the /REMOTE parameter was specified on the command line, the remote port forward was not established.
  • Windows: For all dialogs, tooltips were added to buttons without text labels in order to provide button information for screen readers such as JAWS.
  • Mac: Buttons or keys mapped to the menu functions MENU_RECEIVE_ASCII, MENU_SEND_ASCII, or MENU_SEND_BINARY did not work.
  • Mac: On 10.9 (Mavericks), the text on button labels and list views was not aligned correctly.
  • Mac: On 10.9 (Mavericks), disabled menu items appeared to be available instead of being grayed out.

New in version 7.2.2 (March 24th, 2014)

  • Bug fixes:
  • If a folder with the same name as an existing session was created in the same location as the session and the session was moved into that folder and then moved into the Sessions folder, the session was changed to a folder.
  • If the session manager was unpinned and then closed, the area in the session where the session manager had been no longer scrolled.
  • The command (chat) window history did not work.
  • The Quick Connect dialog was not displayed at startup when the option "Show Quick Connect at startup" was set.
  • Windows 8: SecureCRT crashed when attempting to upload or create a new key using the public-key assistant.
  • Changes:
  • Reverted the following change: The xterm keymap now sends Esc[H and Esc[F for Home and End.

New in version 7.2.1 (January 18th, 2014)

  • Bug fixes:
  • SecureCRT hung when a Python script tried to disconnect a session that had the "Close on disconnect" option set.
  • When multiple sessions were selected in the Connect dialog or session manager using the SHIFT or CONTROL keys, sessions could incorrectly be unselected.
  • Mac: If an incorrect password was saved in the keychain, it was not possible to save the correct password when using keyboard interactive authentication.

New in version 7.2.0 (December 13th, 2013)

  • Changes:
  • Added the ability to specify what port the TFTP server listens on.
  • Bug fixes:
  • SSH2: SecureCRT could crash if the SecureCRT application was closed while connecting to a session that used public-key authentication.
  • Mac/Linux: If a session that started the TFTP server was connected and a local shell session was connected and disconnected and then the first session was disconnected and reconnected, the TFTP server could not be started because the port was already in use.

New in version 7.2.0 Beta 5 (December 6th, 2013)

  • Bug fixes:
  • SecureCRT crashed if a password for a session that displayed an authentication banner at logon was changed in the Session Options dialog when the session was not connected.
  • The Arguments.Count script property did not return the correct number of arguments for logon scripts.
  • If the session manager was docked and unpinned and the SecureCRT window was maximized, when SecureCRT was closed and restarted, the session manager was unhidden on startup.
  • If the session manager was docked in the bottom pane next to the command window, the title bar was displayed in the command window.
  • If the session manager was docked next to the command window, it's position was not stored correctly when SecureCRT exited.