SecureCRT Changelog

New in version 7.3.4

June 17th, 2015
  • Bug fixes:
  • If a tabbed session was closed while a transfer operation in that
  • session was in progress, SecureCRT crashed.
  • When SecureCRT and SecureFX were integrated, if the configuration
  • passphrase was changed in one application while the other
  • application was running, the sensitive data could have been
  • encrypted incorrectly.
  • The personal data folder could not be merged with the configuration
  • folder if the personal data folder contained any empty session
  • folders.
  • When the Session Manager was in autohide mode and a session was
  • connected, if a menu was activated using the keyboard and dismissed
  • by pressing ESC, and then the keyboard accelerator to display the
  • Session Manager was pressed, the Session Manager gained focus but
  • remained hidden.
  • SSH2: SecureCRT could crash when a smart card was used for
  • authentication.
  • Windows: On Windows 10, the last line of the terminal session was
  • partially hidden by the bottom of the application window.
  • Windows: On Windows 10, moving the SecureCRT window caused it to get
  • smaller.
  • Windows: On Windows 10, every time a tiled session was connected, it
  • shrunk by one row and one column.
  • Windows: On Windows 10, if the session rows and columns were changed
  • in the Session Options dialog, the view size was one row and one
  • column less than the specified values.
  • Windows: PKCS11 authentication failed with FortiToken ePass2003.
  • Windows: CAPI authentication failed with the Fortinet FTK300 token.
  • Mac: Due to a change in OS X 10.10 (Yosemite), there can be more
  • than one $PATH, which meant that the $PATH variable used by
  • SecureCRT might not have contained the expected paths.
  • Mac: If there were multiple SecureCRT application windows, the
  • keyboard accelerators COMMAND+I and COMMAND+M did not work unless
  • the Session Manager was open in all the SecureCRT windows.
  • Mac: The SecureCRT version should not have been displayed in the
  • title bar for official releases.
  • Mac/Linux: In the Manage Agent Keys dialog, if all keys were removed
  • and then the Remove button was pressed again, SecureCRT crashed.
  • Mac/Linux: The Help contents, search, and glossary were not
  • available.

New in version 7.3.3 (April 1st, 2015)

  • New features:
  • Previous versions of SecureCRT supported saving passwords and other sensitive data. In order to improve the security of this feature, SecureCRT now requires a passphrase to be created the first time version 7.3.3 runs. This passphrase will be used to encrypt and decrypt sensitive data stored in the session database, such as passwords and send/expect logon scripts.
  • Bug fixes:
  • SecureCRT hung if logon actions were being edited for multiple sessions and one of the strings being replaced was blank.
  • The crash reporter dialog, which reports crashes for previous runs of SecureCRT, was being displayed after the SecureCRT window was displayed, which caused confusion about when the crash had occurred.
  • SSH1: If the "Auto reconnect" global option was set and a session that did not have the username and/or password saved got disconnected, if the user did not respond to the username or password prompts, multiple prompts were displayed until SecureCRT eventually crashed.

New in version 7.3.1 (December 17th, 2014)

  • Changes:
  • In order to address the POODLE attack, SSL 3.0 is disabled by default.
  • SSH2: When using public-key authentication, if the .PUB file is not present, it is created automatically so that agent will work.
  • Bug fixes:
  • SecureCRT could hang when attempting to stop using a personal data folder.
  • Quotes were not supported in regular expressions used for keyword highlighting.
  • If the global option "Exit when last session is disconnected" was set and the session option "Clear on disconnect" was set for a session and that session was connected twice, if one of the sessions was disconnected, it was not cleared.
  • It was possible to activate the menu bar using a keyboard accelerator when the menu bar was disabled.
  • Windows: The 32-bit version of SecureCRT could crash when the "Prompt send delay" option was set for the session and text was pasted into the session.
  • Windows: The "Default.mnu" file did not include "Update Now" in the Help menu.
  • Mac: SecureCRT crashed when attempting to create a Telnet session that used an SSH1 or SSH2 session as a firewall.
  • Mac: X11 forwarding did not work with XQuartz on Mac OS 10.10 (Yosemite).
  • Mac/Linux: After dragging a tabbed session within the application window to change its order, it was no longer possible to drag a tabbed session to a different window.
  • Mac/Linux: SecureCRT did not honor the shell setting for a local shell when it was set by the "chsh" command.
  • Mac/Linux: If focus was in the session manager when it was closed, it remained there.

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.

New in version 7.2.0 Beta 4 (November 21st, 2013)

  • Changes:
  • Added the ability to map keys and buttons to zoom in and zoom out.
  • Bug fixes:
  • An error was reported during a Kermit upload when the INIT response packet contained an "N" in the prefix field to indicate that prefixing was not supported by the Kermit server.
  • When the session manager was on, if a session that prompted for the username was connected, the username was cached when the "Save username" check box was unchecked.
  • The SecureCRT window did not zoom when CTRL+"+" was pressed.
  • It was not possible to map CTRL+"+" and CTRL+"-" to be disabled.
  • Windows: An error was reported during a Kermit upload over a serial stream if the first packet's data was queued, because only 6K out of 9K of data was sent.

New in version 7.1.3 (November 11th, 2013)

  • Bug fixes:
  • SecureCRT could crash if it was running inside an embedded window in Remote Desktop Manager and the RDM tab was closed.
  • If a session was scrolled back so that older output was shown and Print Screen was selected, the most recent output was printed.
  • When a firewall was specified on the command line or in a script, if the session reconnected, the specified firewall was not used.
  • The scripting function SetOption("Cols", nCols) failed to set the columns to specified value.
  • The scripting function ActivePrinter failed to set the active printer.
  • When tiled sessions were being used, the accelerators for "Port" and "Open in a tiled window" in the Quick Connect dialog were the same.
  • SSH2: If a session was closed before public-key authentication completed, SecureCRT could crash.
  • Mac: When text was pasted into a session, it was sometimes doubled or tripled.
  • Mac: If the option "Ignore window title change requests" was set and a tabbed session whose title had been changed was moved between windows, the title bar was reset to the default title.
  • Mac: If a previous version of SecureCRT 7.1 had been installed in a location other than Applications and a newer version of 7.1 was installed, the Help file could not be loaded.
  • Mac: The Session Wizard dialog was missing the wizard image.
  • Mac/Linux: SecureCRT crashed when attempting public-key authentication if the key was larger than 2048 bits.

New in version 7.2.0 Beta 3 (November 11th, 2013)

  • Changes:
  • A progress indicator is displayed when personal data is being separated or merged.
  • SSH1/SSH2: The length of the Secure Shell identity string was reduced in order to be compatible with non-compliant servers.
  • Mac/Linux: The personal data folder now has a default instead of being empty.
  • Bug fixes:
  • The personal data folder option did not honor environment variables.
  • The SessionConfig scripting object's Save function did not work.
  • Mac/Linux: The session hover text was incorrect when multiple sessions were connected.

New in version 7.1.2 (August 9th, 2013)

  • Changes:
  • With WYSE50 emulation, when the remote system sent ESC * or ESC +, the reverse video attribute could remain set. SecureCRT now clears the display attributes when those escape sequences are received.
  • Escape sequences specifying that the entire display should be erased are now ignored when they contain an invalid parameter.
  • Added a global-file-only option "Log Uses Generic Write Flag" so that logging works with sessions that connect to a network drive that does not support the FILE_APPEND_DATA flag, such as Novell NSS.
  • Bug fixes:
  • SecureCRT did not correctly handle the xterm-256 color escape sequence CSI38;5;196;4;1m.
  • In the "Session Options" dialog, if the background color of the color scheme was changed, it was not saved.
  • In the "Connect" dialog, the right-click menu item "Find" did not work.
  • The pass-through printing termination sequence was not being honored.
  • Pressing the "Advanced" button in the "GSSAPI" dialog caused the dialog to move.
  • Windows: On Windows 7, it was not possible to run the modem control panel.
  • Mac: Sending chat text to all sessions did not work if focus was switched to another application and then back to SecureCRT.
  • Mac/Linux: The global INI-file-only option "Is Full Screen" was not being honored.

New in version 7.1.1 (May 31st, 2013)

  • Bug fixes:
  • SecureCRT hung if a script called Screen.CurrentColumn or Screen.CurrentRow before user authentication had completed.
  • If a button was given a label that included an ampersand (&), the ampersand was not shown correctly on the button.
  • If a button bar was given a name that contained an ampersand (&), the ampersand was dropped.
  • Windows: SecureCRT could take a long time to start if there were a large number of autostart sessions and the tab status indicator option was set to "Background colors".
  • Windows: If a button bar other than "Default" was selected in the default session, that setting was not honored.
  • Mac: SecureCRT crashed after opening over 20 connections in new windows and then selecting the Window menu.
  • Mac: If a large number (e.g., more than 100) of port forwards were specified for a session, SecureCRT could crash or report the error "Too many open files" when attempting to establish the port forwards.
  • Mac: If SecureCRT and SecureFX were installed into a path that contained a space, when the toolbar button to launch SecureFX was pressed, nothing happened.
  • Mac: If the status indicators "Color rectangles" were selected, the rectangles were not positioned correctly on the tab.
  • Mac: If a tab was given a label that contained an ampersand (&), the ampersand was dropped.
  • Linux: Kubuntu 13.04 crashed when running SecureCRT 7.1 due to a mismatched Qt library.

New in version 7.1 (May 3rd, 2013)

  • This version brings tiled sessions to the Mac and Linux versions, adds an option to set up dependent sessions for connecting with jump hosts, and extends file transfer options with Kermit support.
  • Productivity improvements include the ability to send a button bar command to all sessions and to optimize the data transfer speed with a new send delay option.
  • On the Windows platform, this release supports SHA1 in RSA signatures, which allows X.509 certificates to be used in FIPS mode.

New in version 7.0.4 (April 20th, 2013)

  • This version adds various bugfixes.

New in version 7.0.3 (January 18th, 2013)

  • In the Connect dialog, if a folder was renamed to a string that ended in one or more "." characters, the sessions in the folder were deleted.
  • Opening the default session in a script caused SecureCRT to crash.
  • If the "Automate logon" items for a session were re-ordered, the changes were not saved.
  • If "/Serial" or "/Tapi" (Windows only) was specified on the command line, it was not honored.
  • If a session that contained ANSI color text in the scrollback was disconnected and reconnected, the ANSI color attributes were no longer in the scrollback.
  • When enough tabs were open to require the scroll control on the tab bar, if the right-most tab was activated and renamed, the tab bar shifted to the left and the active tab was no longer visible.
  • Serial: The stop bits were not logged correctly in the trace output.
  • SSH1/SSH2: If a session used a dynamic tunnel on port 10080 and another SSH1/SSH2 session went through the first session's SOCKS proxy and used a dynamic tunnel on port 1080, SecureCRT crashed when data went through the second tunnel.
  • Windows: When switching between tiled and tabbed sessions in a maximized window, the terminal area was 24x80 instead of the full window area.
  • Windows: If the global option "Minimize to Activator in system tray" was set and SecureCRT was closed, if "Connect" was selected from the Activator menu, the icons in the Connect dialog were not mapped to the correct actions.
  • Mac: The session option "Use ALT as meta key" was not always honored.
  • Mac: If the global option "Host key database location" was changed to a different path, the new path was not saved.
  • Mac: If a session prompted for a log file, after the file location was selected, focus did not return to the SecureCRT window.

New in version 7.0.1 (August 29th, 2012)

  • Changes:
  • The xterm set title escape sequence ending with \033\\ is supported in addition to \007.
  • Bug fixes:
  • If the username was sent to a session after the connection was gone, such as when the server had a short authentication timeout, SecureCRT crashed.
  • Hostkey database paths that contained "%USERPROFILE%" were not expanded correctly.
  • If a disconnected session had focus and other tabbed or tiled sessions were connected and the "Show confirm disconnect dialog" option was set, SecureCRT did not display the disconnect prompt when the application was closed.
  • Windows: SHIFT+INSERT could not be used to paste into the Connect bar.
  • When SecureCRT and SecureFX were integrated, if the configuration folder contained "%APPDATA%", attempting to launch SecureFX from the SecureCRT toolbar caused an error to be reported.
  • The ConnectInTab script function did not honor the "Reuse disconnected tabs" setting.
  • Windows: After maximizing and restoring a tiled session, the output was displayed in only the top half of the session window.
  • Windows: When a SecureCRT session was launched from the Windows 7 task bar "Connect..." menu item, it was displayed behind all other application windows.
  • Windows: A custom menu file configured in SecureCRT 6.7 did not take effect after installing version 7.0 until SecureCRT was closed and restarted.
  • Windows: When SecureCRT started in tabbed mode after switching between tabbed and tiled windows that connected sessions with small sizes, the application window was smaller than the specified session size.
  • Windows: When the Windows 7 task bar was not in the default location, and SecureCRT switched from tiled to tabbed mode, the tab bar was not in the correct location.
  • Windows: The New Session wizard allowed a session to be created with a name that was a Windows reserved keyword, such as COM1 or LPT1.
  • Mac: SecureCRT could not be installed on OS X 10.8 (Mountain Lion) without disabling the gatekeeper.
  • Mac: After creating a new or editing an existing color scheme, the Global Options dialog became unresponsive.
  • Mac: SecureCRT could hang when configuring the tab status indicator rectangle colors.
  • Mac: Pressing CTRL+TAB or CTRL+SHIFT+TAB did not switch to the next or previous tabs, respectively.
  • Mac: When SecureCRT was minimized to the dock, it could not be restored by left-clicking it.
  • Mac: On OS X 10.8 (Mountain Lion), SecureCRT could not locate crash dump files because they were being created in a different folder than in previous versions of OS X.
  • Mac: The title bar was displayed in full-screen mode.
  • Linux: SecureCRT prompted when the log file existed, although the "Append to file" option was set.

New in version 7.0 (July 10th, 2012)

  • This version adds tiled sessions on the Windows platform for easy viewing of multiple sessions.
  • On all platforms, a built-in TFTP server provides an additional option for file transfers.
  • Connect dialog performance has been significantly improved.
  • Changed passwords are automatically updated in the Mac OS X Keychain.
  • It's now possible to skip authentication methods such as PublicKey and GSSAPI which might not be supported or configured on some systems.
  • Enhancements have been made to mapped buttons and keys.

New in version 7.0 Beta 1 (May 5th, 2012)

  • SecureCRT 7.0 introduces tiled sessions on the Windows platform for easy viewing of multiple sessions.
  • On all platforms, a built-in TFTP server provides an additional option for file transfer and enhancement to authentication and mapped button and key options.

New in version 6.7.5 (April 20th, 2012)

  • When the emulation was set to "Xterm" and the option "Send scroll wheel events to remote" was set, in vi or vim, it was not possible to scroll down using the mouse scroll wheel.
  • Windows: When the system used the Microsoft HID-compliant mouse driver and the mouse was configured to scroll one screen at a time, SecureCRT did not scroll the correct direction when the mouse scroll wheel was used.
  • Mac/Linux: When a button was added to the button bar while a session was connected, the session size decreased.
  • Linux: On Ubuntu Linux, the evaluation was not extended after the evaluation extension data was entered.

New in version 6.7.4 (February 3rd, 2012)

  • Linux:
  • SecureCRT for Linux brings the extensive SecureCRT feature set to Ubuntu 10.x, Ubuntu 11.x, RHEL 5.5 and RHEL 6.0. Noteworthy for Linux are local shell access and Python scripting.
  • Connect bar:
  • The Connect bar provides a text entry box to connect to a session quickly without opening a dialog. The Connect bar supports SecureCRT command-line options.
  • Scripting enhancements:
  • Script recorder adds Python support: Automate connections and routines using the Python script recorder, which records keystrokes and then generates a Python script.
  • "Run Script" from a key or button: Map a key or button to browse for a script to run.
  • New scripting functions: The FileOpenDialog() function opens a file browser and returns the selected file. ScriptFullName() returns the full path and filename of the currently running script. The Connect() function adds an optional parameter to allow pop-up messages to be suppressed.
  • Button bar enhancements:
  • Add more than ten buttons to a button bar, copy and paste buttons from one button bar onto another, and move buttons within a button bar.

New in version 6.7.3 (November 9th, 2011)

  • This release features a new Connect bar and many improvements to the button bar and scripting, like Python support in the script recorder and copy and paste for button bar buttons.