SecureCRT Changelog

What's new in SecureCRT 9.0.2 Build 2496

May 20, 2021
  • Change:
  • Windows: The Scratchpad and Script Editor now honor the "Use ClearType to smooth edges of screen fonts" global option.
  • Bug Fixes:
  • When connected to a host using TN3270 emulation, if the current partition was unformatted, the SETBUFFERADDRESS command was unexpectedly included in SecureCRT's response.
  • Windows: If a session was configured to use a firewall that prompted for credentials, and that session was configured to automatically connect at application startup, SecureCRT crashed.
  • Windows: Under certain circumstances, when opening the Session Manager, some folders may not have been expandable.
  • Windows: When authenticating with a PKCS#11 certificate with certain signature algorithms, the key may not have been added to the SSH agent.
  • Windows: Under certain environments, when connecting to an RDP session, the remote display would not scale to match the local desktop.
  • Mac/Linux: If a log file was initially created with the "Append to file" logging option enabled, Unicode characters may not have been logged correctly.

New in SecureCRT 9.0.1 Build 2451 (Mar 19, 2021)

  • Change:
  • Restored the ability to use the SHA1-96 and MD5-96 MACs.
  • Bug Fixes:
  • If a script that made a connection was specified on the command line, a "script is currently running" error was incorrectly reported. The script did run after the dialog was dismissed.
  • When performing a "Find" operation in the terminal view, if the end of the buffer was reached, the search direction could not be reversed.
  • Windows: When a disconnected RDP session tab was reused by a new RDP connection, the title bar text was not updated.
  • Mac/Linux: If the Session Manager was docked and not auto-hidden, sessions could have appeared as duplicated when SecureCRT was launched.
  • Mac/Linux: Under certain scenarios, opening a tab in a new tab group caused the terminal view to be blank.

New in SecureCRT 9.0.0 Build 2430 (Feb 19, 2021)

  • Bug Fixes:
  • When a script was specified on the SecureCRT command line, the error "script is currently running" was incorrectly reported. The script did run after the dialog was dismissed.
  • Windows: If a user was denied remote desktop access on the target system, connecting with an RDP session silently failed without reporting the system error.

New in SecureCRT 8.7.3 Build 2279 (Aug 12, 2020)

  • Bug fixes:
  • When the sample ANSI color palette was shown for a color scheme, the colors displayed did not match the descriptive text for the color (e.g., "ANSI Red" text was displayed using the green color).
  • The display of certain Unicode characters (e.g., emojis) inthe terminal could have caused other characters to appear as clipped.
  • Mac/Linux: Text displayed on the Keyboard Interactive and View Host Key dialogs could not be selected or copied.
  • Mac/Linux: When enabling logging via the File menu, connecting to a session caused logging to be toggled off.

New in SecureCRT 8.7.2 Build 2214 (May 15, 2020)

  • Vulnerabilities addressed:
  • When certain emulation functions received a large negative number as a parameter, it could have allowed the remote system to corrupt memory in the terminal process, potentially causing the execution of arbitrary code or a crash.
  • Bug fixes:
  • If a script was launched from a button bar button or keymap shortcut and the script file could not be located, a misleading error was reported.
  • Mac: Attempting to authenticate using a YubiKey smartcard with the "opensc-pkcs11.so" library specified as the PKCS#11 provider resulted in an error, because the library could not be loaded.
  • Mac: If the ZModem Upload List dialog was using the List view mode, which allows a folder to be expanded to display its contents, a file within an expanded folder could not be added to the upload list. Manager was expanded via the "Connect..." toolbar item, the Session Manager would briefly open, then immediately re-hide.
  • Mac/Linux: If the Command Window option "Send Characters Immediately" was enabled, minimizing and restoring SecureCRT caused the option to be disabled.

New in SecureCRT 8.7.1 Build 2171 (Mar 19, 2020)

  • Changes:
  • The performance of keyword highlighting has been improved to be as fast as and in many cases, much faster, than version 8.5.
  • SecureCRT now handles the Xterm "paste bracketing" escape sequence so that indentation is correct when indented text is pasted into an editor.
  • Added an optional "hide output" parameter to the Session Object Lock() method.
  • SSH2: When doing public-key authentication, if there is no corresponding private-key file without an extension and there is a private-key file with a .ppk extension, it will be used.
  • Mac/Linux: When ENTER is pressed on a folder in the Session Manager, it is expanded or collapsed. Previously, all the sessions in the folder were connected.
  • Vulnerability addressed:
  • TFTP: The TFTP server is off by default. However, when the TFTP server was running, SecureCRT was vulnerable to a directory traversal attack that allowed access to arbitrary files on the local system.
  • Bug fixes:
  • When running a version of the Midnight Commander file manager that supports extended coordinate mouse clicks, mouse operations from within SecureCRT did not work.
  • When multiple screens were created using the "screen" utility, the scrollback from one screen could end up in the scrollback for a different screen.
  • When multiple screens were created using the "screen" utility, the man page output went to the scrollback buffer.
  • In the Manage Agent Keys dialog, the columns expanded every time the dialog opened, which eventually caused all column headers to disappear.
  • If two sessions were connected and then a session was sent to a new window, if the Hex view was opened, no data was displayed in the Hex view for the session.
  • The items "MENU_TOGGLE_KEYWORD_HIGHLIGHTING" and "MENU_CONNECT_LOCAL_SHELL" were not recognized when they were included in a custom .MNU file.
  • Mac/Linux: In the Session Manager, when attempting to give a folder a name that conflicted with an existing folder name, the original or default name was used, instead of allowing a different name to be specified.

New in SecureCRT 8.7.0 Build 2143 (Feb 12, 2020)

  • Change:
  • SSH2: Keyboard-interactive authentication works with a prompt that contains "password" with any combination of upper and lower case letters (e.g., "Password" or "PASSWORD").
  • Bug fixes:
  • When an editor (e.g., vi or vim) was used to edit a file on the remote system, the wrong line could have been deleted when the delete line command was sent.
  • When a session with an authentication banner reconnected, extra newlines were inserted after the banner.

New in SecureCRT 8.5.4 Build 1942 (May 31, 2019)

  • Changes:
  • Updated the version of Python that ships with SecureCRT to 2.7.16.
  • Bug Fixes:
  • Mac: When opening certain dialogs (e.g., Session Options), the dialog may have opened in the upper left corner of the monitor, instead of centered over the main window.

New in SecureCRT 8.5.3 Build 1867 (Feb 13, 2019)

  • Change:
  • Treat the [email protected] key-exchange algorithm as synonymous to the curve25519-sha256 algorithm.
  • Bug fixes:
  • Under certain circumstances, tiled session did not resize correctly after resizing the Command window.
  • If the default session protocol was set to something other than TAPI and the Quick Connect protocol was changed to TAPI, attempting to configure TAPI produced an error.
  • If the Screen.get2() scripting function was called, line drawing characters in the terminal window could be corrupted.
  • When a large scrollback buffer was configured, the scroll bar could get stuck at the top of the scrollback.
  • SecureCRT now prevents multiple Connect bars from being added to the toolbar.
  • SSH2: If the public key in use was generated with the ssh-keygen -Z option, SecureCRT could crash when attempting to enter the passphrase.
  • Mac/Linux: The Session Manager was always shown at startup even if it was closed prior to closing SecureCRT.
  • Mac/Linux: If a logon script was running in a session and a large amount of output was received, not all of the output was displayed.
  • Mac/Linux: If a script was launched using a mapped key, the menu item "Cancel" was not available on the Script menu.
  • Mac: If the global options "Paste on middle button" was set, the Confirm Paste dialog continued to be displayed after the Cancel button was pressed.
  • Mac: The Zmodem Upload List browse dialog did not honor Chinese characters.
  • Mac: When using a Wacom tablet and stylus as the mouse, the mouse pointer would not always reappear in the expected location.
  • Mac: If text with trailing newlines was pasted into the Connect bar, the text was not visible.

New in SecureCRT 8.5.2 Build 1799 (Nov 23, 2018)

  • New feature:
  • Added support for the curve25519-sha256 key-exchange algorithm.
  • Bug fixes:
  • If an OpenSSH format key was manually added to the host key database, SecureCRT crashed when attempting to connect to a host that used that key.
  • If the Session Manager was pinned and the active session had keyword highlighting on and it was toggled off by selecting "Keyword Highlighting" from the Options menu and then the Session Manager was hidden, keyword highlighting was re-enabled.
  • Mac/Linux: If the Session Manager was undocked and redocked, the terminal area size changed.
  • Mac: SecureCRT could crash if a session had a dependent session and the wrong password had been saved for both sessions and the wrong password was entered when attempting to connect to the session.
  • Mac: If CTRL+ was used to select multiple folders in the Session Manager or Connect dialog and then arrow keys were pressed, the selection could not be cleared.

New in SecureCRT 8.5.1 Build 1764 (Sep 28, 2018)

  • New feature:
  • Added a new script function FileSaveDialog() that allows saving to a file that does not exist.
  • Bug fixes:
  • If the command line specified a saved session (/S) and overrode the local listening IP address (/LOCAL), an error was reported and the session did not connect.
  • The button bar list was empty if button bars were imported when the button bar list was not displayed and then the button bar was displayed.
  • Mac: After successfully updating using "Update Now" once, SecureCRT could not be updated again using "Update Now".
  • Mac: The dialog for customizing the toolbar was displayed over the toolbar so that items could not be dragged into the toolbar.
  • Change:
  • Mac: Dark Mode is disabled due to incompatibilities with MacOS 10.14 (Mojave).

New in SecureCRT 8.5.0 Build 1740 (Aug 28, 2018)

  • Bug fix:
  • SecureCRT could crash if a new folder was created in the Session Manager or Connect dialog and there was at least one other folder under "Sessions" and then sorting was changed to manual arrangement and a session was dragged to be between the "Session" folder and the top folder.

New in SecureCRT 8.5.0 Build 1731 Beta 5 (Aug 16, 2018)

  • Bug fixes:
  • Mac: When SecureCRT and SecureFX were integrated, if both SecureCRT and SecureFX were running and connected to a session and then SecureCRT was launched from SecureFX, the current session was opened in a tab in the SecureCRT window and in a new SecureCRT window.
  • Mac: SecureCRT could, under rare circumstances, crash when "Page Setup" was selected from the File menu.

New in SecureCRT 8.5.0 Build 1724 Beta 4 (Aug 9, 2018)

  • Bug fixes:
  • Scripts specified in custom keymaps and mapped keys were not included when settings were exported and imported.
  • The Beta expiration notice was displayed more frequently than it should have been when SecureCRT was not closed and other instances of SecureCRT were started/opened/launched.
  • Mac: If settings were exported to a network share (SMB), the XML file was blank.
  • Mac: If a session was imported from another platform and the session's font did not exist on MacOS, the terminal text was not displayed correctly.
  • Mac: When a session was configured to use GSSAPI authentication, if GSSAPI authentication failed, a warning dialog to this effect was still displayed when "Do not show this message again" was checked.
  • Mac: When the Confirm Multi-Line Paste dialog was displayed, focus was in the edit box instead of on the Paste button.

New in SecureCRT 8.5.0 Build 1707 Beta 3 (Jul 20, 2018)

  • Bug fix:
  • When the script recorder was used to generate a Python script, escape characters [chr(92)] were not included in the script.

New in SecureCRT 8.3.4 Build 1699 (Jul 13, 2018)

  • Bug fix:
  • When the script recorder was used to generate a Python script, escape characters [chr(92)] were not included in the script.

New in SecureCRT 8.5.0 Build 1689 Beta 1 (Jul 6, 2018)

  • New features:
  • Added a Button Bar Manager, which allows button bars to be added, duplicated, edited, deleted, and arranged manually or alphabetically.
  • Added a Button Manager, which allows buttons on a button bar to be rearranged, edited, added, deleted, copied, and pasted.
  • Added the ability to rename button bars.
  • Button bars can be duplicated from the button bar context menu and in the Button Bar Manager.
  • Added the ability to map a button or key to a button bar, making it easier to switch between different button bars.
  • The text in the multi-line paste confirmation dialog can be edited before it gets pasted into a session.
  • The multi-line paste confirmation dialog can be resized.
  • Added the ability to save sessions that were created using Quick Connect, the Connect bar, or the command line.
  • Added a new Script status indicator so that tabbed and tiled sessions can indicate that a script is running.
  • Added a global option to disable all printing.
  • Added a global option that allows the Command window to be configured to send commands to all sessions, visible sessions, or the active session by default.
  • Added the ability to make the width of session tabs a fixed number of pixels.
  • Added support for the SHA2-512-EtM and SHA2-256-EtM MACs.
  • ssh-add can be used to add keys from a remote Linux, Unix, or Mac system to SecureCRT's agent using agent forwarding.
  • Added the ability to specify the quote character(s) to be used for the "Paste as Quotation" operation.
  • Added a global option to prevent numbers from being appended to tabbed or session names when the same session is connected more than once.
  • Added "Reset Name" to the tab/tile context menu, which resets the tabbed or tiled session name back to the session's name or title specified in the Session Options dialog.
  • Added the ability to toggle keyword highlighting from the Options menu.
  • When a session is copied in the Session Manager or Connect dialog, the session's hostname is put in the clipboard so that it can be pasted into a session or other applications. The session can still be pasted into the Session Manager or Connect dialog.
  • Added a global option to disable ALT+ tab switching.
  • Added a global option for triple clicking to include the EOL character in the selection.
  • Sorting on columns is supported in all list controls that have columns.
  • Added a session INI-file-only option "Keyboard Interactive Prompt" that allows the expected prompt for keyboard-interactive authentication to be specified.
  • Added a command-line flag /KEYBOARDINTERACTIVEPROMPT that allows the keyboard interactive prompt to be specified for SSH2 sessions.
  • Added a global INI-file-only option "TFTP Resend Timeout" that allows the resend timeout for the TFTP server to be configured.
  • Mac: Added a global option to automatically set locale environment variables for the local shell. This option is on by default.
  • Changes:
  • Because of an update to a cryptographic library used by SecureCRT, newly generated DSA keys are now restricted to 1024 bits.
  • In the Public Key Properties dialog, the "Use identity or certificate file" field can be left blank.
  • The Full Reset and Soft Terminal Reset escape sequences are now honored with Linux, VShell, VT220, VT320, and Xterm emulations.
  • The DECSUSR escape sequences to change the cursor style are now honored in Xterm emulation.
  • Preceding and trailing whitespace is removed from hosts entered in the Connect bar.
  • Made it easier to specify xterm-256color emulation in the Session Options dialog.
  • Added base color support for TN3270 emulation.
  • If the global option to paste on press of middle mouse button is set, the middle mouse button can be used to paste into the Command window.
  • An optional confirmation dialog is displayed on the "Paste as Quotation" operation.
  • If the session option "Forward X11 packets" is set and no X server is running on the local machine, a warning dialog is no longer displayed.
  • If the session options "Automate logon" and "Send initial carriage return" are set and no Send strings are specified, the initial carriage return is sent when the session connects.
  • The session option "Disable initial SFTP extensions" can now be configured in the GUI.
  • The local and remote port forwarding fields in the Session Options dialog have been made taller so that more configured port forwards are visible.
  • Added the ability to specify the terminal type on the command line using the flag /TERMINAL_TYPE.
  • When the options /COLOR_SCHEME and /T are used on the command line, the color scheme is only applied to the session specified by /T.
  • SSH1/SSH2: If the option "Do not request a shell" is set, a message to that effect is displayed in the session.
  • Windows: For the VS2018 Dark theme, the active tab's color was lightened so that it would stand out more.
  • Windows: The close button for the "Native" display theme is now a plain "X".
  • Mac: The Expose (Command+Shift+) behavior has been disabled.
  • Mac: The Command window can now be resized to be as small as one line tall.
  • Bug fixes:
  • If two instances of SecureCRT were running and the Global Options dialog was displayed in one instance and the Session Options dialog was displayed in the other, if changes were made in the Global Options dialog and saved, SecureCRT crashed when attempting to select a different category in the Session Options dialog.
  • In the Session Manager or Connect dialog, if a folder was renamed to have a name that was too long for the local system, the sessions contained in the folder were deleted.
  • SecureCRT hung when running a Python script that called crt.Screen.Send("00).
  • SecureCRT failed to authenticate with remote systems, such as the Balabit PPM SSH proxy server, that requested the same authentication method more than once during authentication.
  • If SecureFX was also installed and the terminal protocol in the default session was set to None, SecureCRT could not be launched.
  • When the script recorder was used to generate a Python script, escape characters [chr(92)] were not included in the script.
  • When exporting settings, scripts that were used by buttons were not exported.
  • If keyword highlighting was turned on through a script, the terminal window was not updated to highlight the keywords.
  • The multi-line paste dialog did not display the text correctly if the session was using the vt100 font and the configuration data was from a version of SecureCRT between 6.0 and 6.2.
  • Characters in the upper range of Unicode code points, such as emojis and certain Asian characters were rendered incorrectly or as unknown characters in the terminal area.
  • Some double-wide Unicode characters could not be used in keyword highlighting.
  • If SecureCRT was maximized and the Session Manager was made wider, when SecureCRT restarted, the Session Manager's size change was lost.
  • Mac/Linux: In the Map Selected Key dialog, the "Run Script" function was available when scripting was disabled in the Global.ini file.
  • Mac/Linux: SecureCRT reported an error when attempting to log to the same file simultaneously from different sessions.
  • Mac/Linux: The list of hosts in the Global Options dialog in the SSH Host Key category was not sorted.
  • Mac/Linux: If a session name contained two ampersands, the Window and File menus displayed the session name with three ampersands.
  • Mac: Attempting to do a search from the Help menu resulted in an error or a crash.
  • Mac: SecureCRT could crash if it was minimized while the printer was being initialized.
  • Mac: If Option+e was entered, SecureCRT did not exit accent mode if a hotkey was pressed.

New in SecureCRT 8.3.3 Build 1646 (May 3, 2018)

  • New features:
  • Added a global option to disable all printing.
  • ssh-add can be used to add keys from a remote Linux, Unix, or Mac system to SecureCRT's agent using agent forwarding.
  • Change:
  • Mac: The accelerator for resetting the zoom level to 100% was changed to COMMAND+SHIFT+0.
  • Bug fixes:
  • SecureCRT crashed when the remote system tried to write to the VT320 status line, but the VT320 status line had not been enabled by the remote.
  • SecureCRT did not send FIN when disconnecting Telnet sessions.
  • If the SecureCRT window was maximized and then minimized and restored, when a session was connected, the window was restored instead of remaining maximized.
  • The hostname was not remembered if the protocol was changed from SSH2 to Telnet when the Connect bar was used to connect to a remote system.
  • In Python scripts, the Session object method "Unlock" did not work.
  • Windows: On Windows 10, if RDP was used to connect to a machine running SecureCRT with a session connected and then RDP was disconnected, SecureCRT crashed.
  • Mac: If focus was in the Connect bar and text was entered causing the auto complete dropdown to be displayed, SecureCRT crashed if it was closed using the red "X".
  • Mac: If the user didn't have write permission to the /cores file, a warning was displayed when SecureCRT started.
  • Mac: Keymapping did not work correctly when a key was mapped to COMMAND+X.
  • Mac: In the Color Scheme dialog, the scrollbar thumb became unresponsive when it was dragged to scroll the ANSI colors list.
  • Mac: In a Python script that created a message box with "Yes" and "No" buttons, the default button could not be set to "No".
  • Linux: On Ubuntu, after selecting a session in the Session Manager or Connect dialog, it could take a long time to connect the session or display the session's properties.

New in SecureCRT 8.3.2 Build 1584 (Feb 8, 2018)

  • Bug fixes:
  • SecureCRT crashed when ALT+ was pressed and no sessions were open.
  • When using Quick Connect, if a firewall that was just created was specified, the firewall was not used when the session connected.
  • Extracting a public-key file from a private key failed with ECDSA keys that were created with ssh-keygen.
  • When a session contained output and was scrolled back half way, if ALT+ was used to do a column select, the selection would not scroll beyond the visible terminal area even though there was output below.

New in SecureCRT 8.3.1 Build 1537 (Dec 7, 2017)

  • Changes:
  • Added default key mappings to Xterm emulation for CTRL+HOME, CTRL+END, CTRL+SHIFT+END, CTRL+SHIFT+HOME, SHIFT+HOME, SHIFT+END, SHIFT+PGUP, and SHIFT+PGDN.
  • Linux: Added the ability to map CTRL+TAB to a key.
  • Bug fixes:
  • SecureCRT crashed if the pre-defined color scheme "Solarized Light" was deleted.
  • If a dialog was displayed while attempting to open a log file when connecting to a session and the session attempted to automatically reconnect before the dialog was dismissed, SecureCRT crashed when the dialog was dismissed.
  • The performance of scrolling large amounts of data with keyword highlighting and the "Minimize drawing" option set was significantly slower than in version 8.1.
  • In the multi-line paste dialog, the clipboard text was very small on high-DPI monitors.
  • Windows: SecureCRT could not be installed on Windows Server 2008.
  • Windows: If the Connect bar was moved to the menu bar using the Customize dialog, auto complete in the Connect bar no longer worked.
  • Windows: Many dialogs had display issues on high-DPI monitors when the system was scaled to 125% or 175%.
  • Windows: The keymap editor dialog had some alignment issues on high-DPI monitors when the system was scaled to 111%.
  • Mac/Linux: When SecureCRT was in tiled mode, if a Python script requested the Tab Object property Index, the value returned was not correct.
  • Linux: On Ubuntu 16, the mouse pointer was very small on high-DPI monitors.

New in SecureCRT 8.3 Build 1509 Beta 4 (Nov 3, 2017)

  • Bug fixes:
  • SecureCRT could crash if a script was attempting to connect to a Serial session in one window while another window was attempting to connect to a Serial session and both were using the same serial port.
  • If a button in the Button bar was mapped to run a script or launch an application that was not located in the SecureCRT install folder, after SecureCRT closed and restarted, the script or application field was blank.
  • Forward slashes specified in the Arguments field in a Button bar button that launched an application were converted to backslashes.
  • When Find was used to search for text in a session and the Find dialog was left open, if the screen and scrollback were cleared, attempting to find text using the Find dialog did not work.
  • When options that should take effect immediately were changed in the Default session and applied to all sessions, the changes were not honored until a reconnect occurred.
  • The script method Config.Save() could not be used to overwrite existing sessions.
  • When SecureCRT and SecureFX were integrated and the "Cache session password" option was on, if quick connect was used to connect to an SSH2 host that used password authentication and then SecureFX was launched, automatically connecting to the same SSH2 host, the password had to be re-entered.
  • Mac: SecureCRT crashed if the Find dialog was open and the session tab that was active when it was opened went away while the Close button in the Find dialog was being clicked.
  • Mac: If COMMAND+ENTER was mapped to Mapping Disable, the application still went into full-screen mode when COMMAND+ENTER was pressed.
  • Mac: Switching between tabs could be slow when there was no default printer.
  • Mac: Specifying a Korean log file name by selecting "Log Session" from the file name resulted in a corrupted log file name.
  • Mac: If SHIFT+ENTER was pressed in the Session Manager, pressing ENTER to connect a session no longer worked until SecureCRT was restarted.
  • Mac: After connecting and disconnecting a session, if a session was connected using the Connect bar, focus remained in Connect bar.

New in SecureCRT 8.3 Build 1491 Beta 3 (Oct 13, 2017)

  • Change:
  • The button bar now uses a templated path, which gets modified to an appropriate path on each platform, for script paths.
  • Bug fixes:
  • When the script function WaitForKey was called with a timeout value, it always returned False.
  • The Move up and Move down icons in dialogs did not display correctly on high-DPI monitors.
  • Windows: SecureCRT crashed in the Windows 10 Creators Update when a smart card (PIV/CAC) was used.
  • Mac: The menu bar contained two Help menus.
  • Linux: The Table of Contents was missing from the online Help.

New in SecureCRT 8.3 Build 1483 Beta 2 (Oct 4, 2017)

  • Change:
  • Mac/Linux: Added "Open SecureFX" to the tab context menu when SecureFX is integrated with SecureCRT.
  • Bug fixes:
  • Mac: If SecureCRT was maximized on a second monitor and closed using the red "X": button, it was not maximized the next time it was launched.

New in SecureCRT 8.3 Build 1474 Beta 1 (Sep 22, 2017)

  • New features:
  • Added several new built-in color schemes, including the Solarized color schemes. There is a variety of light and dark color schemes, all of which have coordinated background, foreground, and ANSI color combinations.
  • Multiple global ANSI color palettes can be defined and a specific color palette can be specified for a color scheme.
  • Added autocomplete to the Connect bar in the toolbar, which makes finding and connecting to saved sessions easier.
  • When the SecureCRT window is resized, the text in the terminal area is rewrapped if the "On resize" option is set to "Synchronize view to size".
  • A paste confirmation dialog option allows you to preview the contents of the paste buffer before pasting multiple lines of text into a session.
  • Multiple sessions can be dragged and dropped or copied and pasted in the Session Manager and Connect dialog.
  • SSH2: Added support for the ChaCha20/Poly1305 cipher.
  • SSH2: Added support for the AES-GCM cipher.
  • SSH2: Added support for the UMAC-128 MAC algorithm.
  • SSH2: Added the ability to use OpenSSH certificates for authenticating SSH2 sessions.
  • SSH2: If a session cannot be cloned or connected using SFTP on the existing SSH connection, SecureCRT will create a new connection.
  • Added a tab context menu item that closes all sessions in the current tab group.
  • Added the ability to script session locking from the Session object.
  • Added a substitution parameter %F that can be used to specify the session's subfolder in a log filename.
  • Added a command-line option /FORWARDX11PACKETS to enable X11 forwarding.
  • Platform-specific configuration settings such as font and window position are now stored separately for each platform which is helpful if settings are saved on a network drive and used on different platforms.
  • Windows: Added an Administrative Policy option to disconnect sessions authenticated using CAPI/PKCS#11 when the corresponding smart card is removed.
  • Windows: Added the ability to hide the title bar for the Command window.
  • Mac: Added an "Update Now" menu item to see if a new version of SecureCRT is available and if there is, clicking a button downloads and installs it.
  • Mac: Arguments can now be passed to a local application that is launched when a tunnel is established.
  • Changes:
  • Up to 20 sessions can be included on the recent session list.
  • Middle clicking on the title bar of a tiled session closes the session.
  • Added a global INI-file-only option to specify the script path.
  • The session level ANSI colors were removed since multiple global ANSI color palettes can be created.
  • SSH2: Modified the default authentication order to be PublicKey, Keyboard Interactive, Password, and GSSAPI. This only affects new installations.
  • The session option "Minimize drawing (faster)" is now on by default. This change only affects new installations.
  • The default session filter delay has been changed from 500 milliseconds to 250 milliseconds. This only affects new installations.
  • For SSH1 and SSH2 sessions, if the session option "Backspace sends Delete" is set, the opcode for Erase is set to ^? (delete), which results in stty -a reporting erase = ^? and tells the terminal that the erase character is Delete.
  • The keyboard accelerators ALT+1 through ALT+0 only operate on the current tab group.
  • Added support for the %P logging substitution for Serial sessions.
  • If the global option "Show Session Manager or Connect dialog on startup" is set, the Session Manager is displayed when SecureCRT starts. Previously, only the Connect dialog honored this option.
  • If SecureCRT is launched using the -F command-line parameter or is on a USB drive, the actual configuration path being used is shown in the Global Options dialog.
  • When saving a recorded script, if the file extension is blank, the appropriate .vbs or .py extension is used.
  • SSH2: If a session is using public-key authentication and the key file has not been specified, the user is no longer prompted to specify the file.
  • SSH2: When importing an SSH2 host key, if it's possible to extract the hostname, IP address, and port from the filename, those values will be used as the default values. Otherwise, the default value for port will be set to 22 and the other values will be left blank.
  • SSH2: When being prompted to accept an SSH2 host key, the fingerprints are now shown in a separate dialog.
  • SSH2: Pressing the SHIFT key in the New Host Key dialog allows a host key to be saved once.
  • In the View Host Key dialog, all the fingerprints can be selected at once.
  • In the View Host Key dialog, SHA-2 fingerprints are displayed in base64 in addition to hexadecimal.
  • SSH2: In the dialogs that prompt to accept the host key, the SHA-2 fingerprint is also displayed in base64.
  • SSH2: The trace output shows the SHA-2 host key fingerprint as base64 in addition to hexadecimal.
  • The username used for authentication is now logged in the trace output.
  • Trace output now includes printer initialization information.
  • The Send String field in the Map Button and Map Selected Key dialogs was made larger vertically and horizontally.
  • The X11 forwarding display option can now be configured in the Session Options dialog.
  • Mac: For new installations, the global option "Use keychain" is off by default.
  • Mac/Linux: A custom baud rate for Serial sessions can be entered by typing into the Baud rate field in the Session Options dialog.
  • Mac/Linux: In the Session wizard, the Port name can be entered manually by typing into the Port field.
  • Bug fixes:
  • SecureCRT crashed when the system time went to midnight if the logging option "Start new log at midnight" was set and the log file name contained the substitution parameter %D.
  • Windows: SecureCRT crashed if a session was being configured and the protocol was changed while a TAPI system prompt was displayed.
  • A session could become slow or non-responsive if another session was receiving and logging a lot of output.
  • Filtered searches in the Session Manager and Connect dialog could be very slow when the session database contained thousands of sessions.
  • Using Quick Connect to connect to a Serial session did not work.
  • TFTP transfers failed when an IPv6 address was used for the remote system (macOS Sierra uses IPv6 addresses by default.)
  • When an illegal character, such as a colon, was used in a log file name, logging failed silently. Illegal characters can no longer be used in a log file name.
  • In the New Session wizard and the Quick Connect dialog, once a session was selected as the Firewall, "Select Session..." was no longer in the Firewall dropdown list.
  • If a session was configured to start logging upon connect and "Log Session" or "Raw Log Session" was selected from the File menu before connecting to that session, logging was turned off.
  • If a button bar name was empty or contained a quote character ("), the button bar was not available after SecureCRT restarted. Button bar names can no longer be empty or contain quote characters.
  • Long button bar names were not completely visible in the button bar dropdown list.
  • If a value larger than 32,000 was entered as the maximum number of columns in the Global Options dialog, no error was reported and a smaller value was used.
  • Attempting to modify protocol-specific options after changing the protocol for a SessionConfig object in a script did not work.
  • If the protocol options /SSH2, /SSH1, or /TELNET were specified on the command line or in the Connect bar without specifying a host, an error was reported.
  • Windows: If a session tab had focus or the mouse hovered over a session tab, pressing ALT+ did not bring up the Windows system menu.
  • Windows: If the Connect bar was showing a dropdown list, pressing ALT+Q displayed the Quick Connect dialog, but did not put focus there.
  • Windows: Some printer setting changes made from the Print Setup dialog were not saved.
  • Windows: On high-DPI monitors, the EULA dialog in the installer did not display correctly.
  • Linux: In Ubuntu 16, toolbar icons and dialog fonts were not displayed properly with high-DPI settings.

New in SecureCRT 8.1.4 Build 1443 (Aug 10, 2017)

  • Changes:
  • Mac: Serial sessions can use higher baud rates such as 921600.
  • Bug fixes:
  • SecureCRT crashed if a button or key was mapped to MENU_GOTO_CONNECT_BAR and the toolbar was customized to remove the Connect bar.
  • When a session specified %USERNAME% as the username and specified another session as the firewall, if authentication failed and the username was changed to something other than %USERNAME%, SecureCRT crashed.
  • SecureCRT could crash if multiple imports of settings ran at the same time.
  • When the configuration folder was being stored in the cloud using services like OneDrive or Dropbox, duplicate copies of __FolderData__.ini could be created and appear as sessions in the Session Manager or Connect dialog.
  • When a regular expression was used for keyword highlighting and the text that matched the regular expression wrapped so that it was on two lines, the text was not highlighted.
  • When SecureCRT was integrated with SecureFX, if SecureCRT was launched from the command line or Quick Connect, it always used SSH2 as the protocol even if the default session specified a different protocol.
  • PKCS #11 authentication failed when using the SuisseID PKCS #11 DLL.
  • When a button was mapped to MENU_SCRIPT_CANCEL, SHIFT+ did not cancel the script on all tabs if the current tab was not running a script.
  • Windows: When "Update Now..." was selected from the Help menu, if a newer version was available, the installer was downloaded to the parent folder of %TEMP%.
  • Mac: If a button was mapped to MENU_SCRIPT_CANCEL, pressing the button when no sessions were open or in a session that was not running a script caused SecureCRT to crash.
  • Mac/Linux: There was no default port specified for new serial sessions.
  • Linux: If a button was mapped to launch an application and arguments were specified, the arguments were not saved.

New in SecureCRT 8.1.3 Build 1382 (May 23, 2017)

  • Bug fixes:
  • Authentication failed when attempting to authenticate using a smart card that contained multiple certificates with blank "Issued to" and "Issued by" fields.
  • Mac: SecureCRT could crash when the computer woke from sleep if the printer initialization failed.
  • Mac: When there were dual monitors and the secondary monitor had a higher resolution than the primary monitor, if SecureCRT started and connected a session and then the SecureCRT application was moved to the secondary monitor and SecureCRT was resized to be almost as large as the monitor, opening the Global Options dialog and dismissing it by pressing the OK button caused the SecureCRT window size to change.
  • Mac/Linux: SecureCRT did not handle PK_OK packets correctly, which caused X.509 authentication to fail.
  • Mac/Linux: Custom ports were not being saved for Serial sessions.

New in SecureCRT 8.1.2 Build 1362 (Apr 28, 2017)

  • Changes:
  • A menu function MENU_SEND_COMMAND_TO_ALL_SESSIONS was added. If this menu function is mapped to a key or button, pressing it causes the value of "Send Command to" to become "All Sessions".
  • Bug fixes:
  • SecureCRT could crash when attempting to access session settings (e.g., from the Session Options dialog) for a session that lost its connection.
  • SecureCRT crashed when attempting to load a certificate from a TIKS card that was inserted in an internal reader.
  • If the menu function MENU_TOGGLE_SEND_COMMANDS_TO_ALL_SESSIONS was mapped to a key or button, pressing it did not do anything if the value of "Send Command to" in the Command window was "All Sessions".
  • Certificate chaining failed for RFC 6187 when using PKCS#11 if the complete chain of certificates was not on the smart card.
  • When performing X.509 authentication to an OpenSSH server with Roumen Petrov's PKIX patch applied, the wrong hashing algorithm was used for generating the signature for an RSA certificate.
  • When using Xmodem to do a file transfer in a serial session, the transfer failed because SecureCRT wrongly changed the parity when the transfer started.
  • Named pipes in serial sessions did not work.
  • For serial sessions, if multiple ports were available and a port other than the first port in the dropdown list was selected in the Session Options dialog and the Session Options dialog was re-opened, the selected port was the first port in the list.
  • Windows: When a theme other than "Native" or "Shaded" was used, if the Session Manager was docked, the scrollbar did not match the theme colors and it flashed when the SecureCRT application window was resized.
  • Windows: SSH agent did not use the algorithm name specified by RFC 6187 if the session used an X.509 certificate stored in a file.
  • Mac: Braille characters were displayed as square boxes if the session used UTF-8 encoding.
  • Mac: If a tab was dragged to create a second tab group and then back to the original group so that there was a single tab group, the terminal size for the active session or all sessions was sometimes incorrect.
  • Mac: When the system keyboard shortcut tab option was set to "Text boxes and lists only," if SecureCRT had focus and then the application window was maximized, SecureCRT no longer had focus.
  • Mac/Linux: If there were multiple tab groups and the SecureCRT application window was maximized and the splitter bar was moved and then the application window was restored, the terminal size was wrong for one or more sessions.
  • Linux: The 32-bit Ubuntu 16.x installer reported an error when attempting to run it on a 32-bit Ubuntu 16.10 system.

New in SecureCRT 8.1.1 Build 1319 (Feb 28, 2017)

  • Changes:
  • The mouse cursor does not need to be inside a selected word in order to choose "Add Keyword" from the right-click menu.
  • Trace output now includes printer initialization information.
  • Mac/Linux: The Session Manager and Connect dialog now use the folder and session icons from the system.
  • Bug fixes:
  • Under certain circumstances, if a command was typed into a session using TN3270 emulation, SecureCRT could hang.
  • For TFTP transfers, SecureCRT incorrectly assumed that if it received a packet it had already received, an unrecoverable block error had occurred.
  • In the New Session wizard, when a hostname was entered as uppercase, it was changed to lowercase when it was saved. The case of the hostname as entered is now preserved.
  • Mac: SecureCRT could crash if it started with the Session Manager enabled and was closed using the red close button while a context menu was displayed.
  • Mac/Linux: It was possible for a session to incorrectly save a font as being scaled, which caused scrolling output to be very slow.

New in SecureCRT 8.1.0 Build 1287 Beta 5 (Jan 18, 2017)

  • Changes:
  • Added a menu function MENU_ADD_KEYWORD that allows a key or button to be mapped to the add keyword operation.
  • Implemented the HOME key for TN3270 emulation.
  • Bug fixes:
  • ECDSA keys with bit sizes of 384 or 521 generated by SecureCRT could not be added to ~/.ssh/authorized_keys using ssh-keygen.
  • TSO logon did not work with TN3270 emulation.
  • Mac/Linux: If there were multiple tab groups and a tab from a single-session tab group was dragged into another tab group, the area from the tab group that was removed was always added to the first tab group.
  • Mac/Linux: Dragging a tabbed session between groups caused the connection status of the other sessions to change to "New Input".
  • Mac/Linux: If multiple tabbed sessions were connected and one of the sessions was sent to a new window, session-specific operations such as copy, paste, print, and reset, were performed in both application windows.
  • Mac/Linux: If there were two tab groups and the tab group separator was resized by dragging the tab group separator, focus was not in any tabbed session.
  • Mac: The COMMAND+X shortcut did not work in the Session Manager or Connect dialog.
  • Mac: The shortcuts COMMAND+C, COMMAND+V, and COMMAND+A did not work in the Connect bar if there were no tabbed sessions.
  • Mac: If a session name contained two or more ampersand characters, when the session name was shown in the File or Window menu, it had at least one extra ampersand.
  • Linux: There was a delay opening the Global or Session Options dialog if the CUPS server was inaccessible.

New in SecureCRT 8.1.0 Build 1261 Beta 4 (Dec 16, 2016)

  • Changes:
  • Mac: By default, core files will not be created if SecureCRT crashes. An option to create core files was added to the Global Options dialog.
  • Bug fixes:
  • SecureCRT could take a long time to start if the default printer was not available.
  • With some print to file options, such as doPDF, bold characters were hard to read.
  • When a script created a new session or folder using SessionConfiguration.Save(), the Session Manager did not refresh the session list.
  • For Serial sessions, the Session Options dialog always chose COM2 as the default port even if nothing was connected to the COM2 port.
  • SSH2: If an RSA key was generated and the .pub file was specified to be used as a raw SSH2 key for public-key authentication, a format error was reported during authentication.
  • Windows: The installer option "Subscribe to Product Announcements" did not work.
  • Windows: If a session name contained an ampersand (&) character, the session name in the tab contained two ampersands.
  • Mac/Linux: If two sessions specified different button bars and the second session was opened in a new tab group, it used the first session's button bar.
  • Mac: If SecureCRT was attempting to find a string in the session and the Find dialog was closed, SecureCRT crashed.
  • Mac: SecureCRT crashed when attempting to dismiss the Password Properties dialog if the global option "Use Keychain" was set.

New in SecureCRT 8.1.0 Build 1241 Beta 3 (Nov 23, 2016)

  • Bug fixes:
  • The Modified Data Tag (MDT) bit was not being handled correctly for TN3270 emulation.
  • When the mouse hovered over the terminal area of a session, the mouse cursor was an edit cursor instead of an arrow cursor.
  • Mac/Linux: If a session was dragged to create a new tab group, the tab that was dragged had the wrong rows and columns.
  • Mac: If system accessibility options were on, SecureCRT could crash shortly after starting or waking from sleep.
  • Mac: The connection status changed to "New Input" when switching between tabs.
  • Mac: On Sierra, SecureCRT could crash when editing the Default session and making changes that brought up the color picker dialog.

New in SecureCRT 8.1.0 Build 1232 Beta 2 (Nov 10, 2016)

  • Changes:
  • Mac: The global option "Disable App Nap to allow background processing" is now on by default. This only affects new installations.
  • Bug fixes:
  • SecureCRT could hang after changing the display theme when there were multiple SecureCRT application windows.
  • If the host key database was on a network share and contained thousands of keys, there was a delay when attempting to display the Global Options dialog.
  • If a script passed a nested directory structure into Config.Save(), the folders in the directory structure were created in the Sessions folder twice.
  • Mac: SecureCRT crashed when attempting to open a keymap file that contained incorrect path separators.
  • Linux: The ALT+M accelerator did not work consistently with the Cinnamon desktop on Ubuntu 15.
  • Linux: When Help was selected from the menu or toolbar, the help file did not load in the browser because the URI was incorrect.

New in SecureCRT 8.1.0 Build 1221 Beta (Oct 28, 2016)

  • New features:
  • Mac/Linux: Added support for tab groups, which provides another option for organizing connected sessions and doing side-by-side comparisons of session output.
  • Mac/Linux: Modified the GUI to look more modern, including new icons for the toolbars in the application window, the Session Manager, and the Connect dialog.
  • Mac: Added support for X.509 certificate authentication using PKCS#11.
  • Added the ability to view session output as hexadecimal in a separate dialog.
  • Added new Command window options to send to selected tab groups or visible tabbed sessions.
  • For Serial sessions, only available COM ports are shown in the drop-down list.
  • Made it easier to add a word to the keyword highlighting list by selecting a word in a session and then right clicking and choosing "Add Keyword...".
  • Added a menu to the tab/tile context menu that closes all tabbed or tiled sessions except for the current session.
  • Added new menu items "Expand All Folders" and "Collapse All Folders" to the Session Manager and Connect dialog right-click menus.
  • Added new menu item "Edit Default Session" to the Options menu.
  • In the Session Manager and Connect dialog, the ENTER and arrow keys can be used when focus is in the filter bar.
  • Xterm emulation now handles the escape sequence for maximizing and restoring the SecureCRT window (CSI 9).
  • Added an option /ConfigPassphrase that allows the configuration passphrase to be specified on the command line.
  • Added a session INI-file-only option called "Raw EOL Mode" which allows CRLF (default), only CR, or only LF to be sent as the EOL for sessions using the Raw protocol or Dumb emulation.
  • Added the ability to pull the username directly from the specified certificate when smart card authentication is being used.
  • Mac: Added a global option called "Disable App Nap." Checking this option allows background processing such as anti-idle to continue when SecureCRT does not have focus.
  • Changes:
  • When doing a filtering search in the Session Manager or Command window, the search does not start until there's a pause in the typing.
  • Locked sessions can now be dragged between tab groups, sent to a new tab group, or sent to a new window.
  • Pressing ALT+I brings up the Connect dialog and puts focus in the filter bar.
  • Hostname resolution now uses the first IP address returned by the system rather than preferring IPv4 over IPv6 addresses.
  • The default terminal emulation is Xterm. This change only affects new installations.
  • When a hostname is used to connect to a session, the IP address is shown in the trace output.
  • SSH2: An INI-file-only "Transport Window Size" was added to allow the SSH protocol window size to be manually set.
  • Mac/Linux: The font dialog only shows monospace fonts.
  • Bug fixes:
  • SecureCRT crashed if an evaluation license expired while SecureCRT was running and an attempt to connect to a session was made.
  • The filtering search in the Session Manager and Connect dialog was case-sensitive for Cyrillic.
  • If the same keyword highlighting list was being used for multiple connected sessions and the list was modified in the Session Options dialog, the sessions were not updated to reflect the keyword highlighting changes.
  • If Trace Options were enabled after connecting to a session that did port forwarding, port forwarding information was not logged in the trace output.
  • When a session was connected, its configuration value "Password V2" was modified unnecessarily.
  • If a session that specified a dependent session was created on a Windows system and then copied to a Mac or Linux system, when attempting to connect to the session, SecureCRT reported that the firewall settings could not be found.
  • Mac/Linux: SecureCRT could crash when dragging the last tab in one window to another window.
  • Mac/Linux: If a session that used the "Scale the font" resize mode was resized so that font scaling occurred and was then restored to 100%, the window size and font were not restored correctly.
  • Mac: The Session Manager could not be resized after it was undocked.
  • Mac: SecureCRT crashed if the Connect bar had focus and the application was put in full-screen mode.
  • Mac: When VoiceOver was enabled, and focus was placed in SecureCRT's Connect bar or the Session Manager's filter bar and a shortcut such as COMMAND+ENTER was typed, SecureCRT hung and the CPU was pegged.
  • Mac: The Session Manager did not correctly handle folder names for some languages, such as Norwegian and Chinese.
  • Mac: If SecureCRT was in the system full-screen mode and the last session was closed using COMMAND+W, the OS X desktop was not restored.

New in SecureCRT 8.0.3 Build 1183 (Sep 9, 2016)

  • Changes:
  • Mac: It is now possible to use a read-only configuration folder. Note: The configuration folder must be writable in order to enter the license data for SecureCRT.
  • Bug fixes:
  • SecureCRT crashed when attempting to export settings that contained a session with a blank name.
  • SSH2: When the SSH2 INI-file-only option "Try All Agent Keys" was set, not all agent keys were tried when connecting SSH2 sessions configured to use public-key authentication.
  • SSH1: Public-key authentication failed when attempting to connect an SSH1 session configured to use an RSA key.
  • Mac: SecureCRT could crash when a Mac laptop woke up from sleep mode.
  • Mac: SecureCRT could crash if the application window was displayed on an external monitor and that monitor was unplugged.
  • Mac: When attempting to connect to a session that was imported from Windows, an error message about the selected font not being fixed width was reported.

New in SecureCRT 8.0.2 Build 1118 (Jun 14, 2016)

  • Bug fixes:
  • If a button was mapped to send the current session to a new window and the button was pressed while another session was being connected, SecureCRT crashed.
  • Keywords were sometimes not highlighted correctly if the remote text contained a tab.
  • With complex keyword lists, the same text could be highlighted differently depending on how the data was received.
  • In SFTP sessions, the mv command did not work when the destination was a folder.
  • Windows: If another application used a DLL called "python27.dll", when SecureCRT started, a runtime error was reported.
  • Windows: Recently uses sessions were not being shown in the Windows Start menu or when the SecureCRT icon was clicked in the Windows taskbar.
  • Windows: If the global option "Only show tabs when there are more than one" was set and a session was cloned and then closed and then cloned again, the height of the SecureCRT window got smaller.
  • Windows: When the session hierarchy contained a lot of nested folders and the Session Manager was configured to auto hide, it opened very slowly.
  • Mac/Linux: The initial window position specified in the session options wasn't being honored.
  • Mac/Linux: The command-line parameter /POS was not being honored.
  • Mac: SecureCRT crashed when attempting to create a session with a name containing Norwegian characters.
  • Mac: Depending on how SecureCRT was launched, the font list in the Session Options dialog could be empty.

New in SecureCRT 8.0.1 Build 1082 (Apr 26, 2016)

  • New features:
  • The color of the icons in the button bar can be configured, allowing buttons to be color coded. This feature was inadvertently omitted from the Beta 1 history.
  • Changes:
  • Pressing ALT+M will open the Session Manager if it's hidden.
  • Pressing ALT+I will display the Session Manager if it's hidden and put focus in the filter bar.
  • Pressing ALT+G on Windows and Linux or ALT+COMMAND+G on the Mac will open the Command window if it's not already open.
  • Added the ability to map the Command window option to send characters immediately (MENU_TOGGLE_SEND_CHARACTERS_IMMEDIATELY) to a key or button.
  • Bug fixes:
  • SecureCRT crashed when importing settings from settings that were exported from SecureCRT 8.0 if the settings contained a button bar.
  • The fallback mechanism for public-key authentication did not work correctly and authentication failed rather than prompting for the username and public key.
  • If a large keyword highlighting list that included regular expressions was used for a session containing a large scrollback buffer, session output could be very slow.
  • The Xterm escape sequence to change the title was not being honored.
  • Pressing ALT+B opened the Session Manager, but did not connect the selected session(s).
  • If the session font was changed before connecting, the old font settings were used when the session was connected.
  • If SecureCRT did not open any sessions on startup and auto-hide was on for the Session Manager, the Session Manager stayed open.
  • Fixed a memory leak that occurred when ECDSA keys were used.
  • Windows: If a tabbed session was closed or disconnected while it was being dragged to a new tab group, SecureCRT could crash.
  • Windows: After connecting to a session using the Session Manager, focus remained in the Session Manager instead of moving to the session.
  • Mac/Linux: SecureCRT crashed when attempting to use the Public Key Assistant.
  • Mac: SecureCRT could crash when the font size for a session was changed in the Session Options dialog by typing in the new font size.
  • Mac: SecureCRT could crash if accessibility options were on and the Session Options dialog was opened several times in rapid succession from the toolbar or the Cancel button was pressed while tabbing through options in the Session Options dialog.
  • Mac: If auto-hide was on for the Session Manager, pressing COMMAND+I did not move focus from the session tree to the session filter box.

New in SecureCRT 8.0.0 Build 1063 (Mar 31, 2016)

  • Bug fixes:
  • Mac: In the Session Manager and Connect dialog, it was not possible to select multiple sessions using COMMAND+.
  • Mac: When outputting a large file with the "cat" command to a session with column width of 256 or larger, the output was noticeably slow.

New in SecureCRT 8.0.0 Build 1055 Beta 5 (Mar 22, 2016)

  • Bug fixes:
  • SecureCRT could crash when keyword highlighting was being used for a session and the session was scrolling output.
  • Zmodem uploads of large files (e.g., 30 MB) could hang.
  • If the configuration paths were set up so that a personal data folder was being used and the configuration folder was read-only, settings could not be saved in the personal data folder even though it was writable.
  • If the configuration paths were set up so that a personal data folder was being used and the configuration folder was read-only, attempting to merge the configuration data failed and the personal data was deleted.

New in SecureCRT 8.0.0 Build 1045 Beta 4 (Mar 12, 2016)

  • Changes:
  • The Session Manager's "auto hide" option is on by default.
  • Bug fixes:
  • If there was text in the scrollback buffer and the session was scrolled all the way back and then the size of the scrollback buffer was decreased in the Session Options dialog, SecureCRT crashed.
  • Files uploaded using Zmodem did not have the correct date and permissions.
  • The progress output from X/Y/Zmodem transfers was formatted incorrectly.
  • When there was a large amount of text in the scrollback buffer and the session window was scrolled all the way back, it was not possible to scroll all the way back down.
  • With the "Office 2013" display theme, if the Session Manager was docked and the SecureCRT application window was maximized and moved to a secondary monitory, the Session Manager could disappear.
  • With the "VS2013 Blue", "VS2013 Dark", and "Office 2013" display themes, if the computer had two monitors and SecureCRT was maximized, the application window extended to the other monitor.
  • The context menu items "Connect in New Tab Group" and "Connect in Tabs" should not have been enabled for tiled sessions.
  • Mac: The Zmodem Upload dialog did not display the upload options by default.

New in SecureCRT 7.3.7 Build 1034 (Feb 25, 2016)

  • Bug fixes:
  • If the Session Manager had Auto Hide enabled and SecureCRT was launched from a desktop shortcut that started SecureCRT minimized, when SecureCRT was restored and the Session Manager was displayed, it was very narrow.
  • If the configuration folder was located on a network drive or contained a large number of sessions, the Session Manager was slow.
  • After importing a configuration that contained a button bar, the button action was not performed when a button was pressed.
  • When upgrading from a version of SecureCRT prior to 6.1, session logon actions were not migrated.
  • When upgrading from a version of SecureCRT prior to 5.0, saved passwords were not migrated to the new version.
  • Mac: SecureCRT could get into a state where it crashed at startup due to an invalid placement of the application window.
  • Mac: SecureCRT could crash if the Session Manager filtered on a string and then filtered on a different string.

New in SecureCRT 8.0 Build 1011 Beta 1 (Jan 29, 2016)

  • New features:
  • Added support for TN3270 emulation.
  • Added support for the VT320 status line.
  • Added a "Send Characters Immediately" mode to the Command window, which makes it possible to do the following in one or multiple sessions: stop commands using CTRL+C, edit files using an editor such as vi, send escape sequences, and do tab completion.
  • Added the ability to start the TFTP server when SecureCRT starts, when any session connects, and manually.
  • Added the ability to use and generate ECDSA (RFC 5656) and Ed25519 keys.
  • Added the ability to generate keys in the new OpenSSH format.
  • SSH2: PuTTY PPK keys can be used for public-key authentication.
  • SSH2: On Windows, enhanced public-key authentication to allow a public key to be specified from the CAPI or PKCS #11 store.
  • SSH2: On Windows, public keys can be exported in OpenSSH format and can be exported from PKCS #11.
  • SSH2: On Windows, certificates can be used as a raw key for public-key authentication.
  • SSH2: On Windows, added support for X.509 authentication using the x509v3-ssh-rsa and x509v3-ssh-dss algorithms as specified in RFC 6187.
  • SSH2: On Windows, X.509 v3 keys can be added to the SSH agent.
  • SSH2: Added an SSH INI-file-only option called "Automatically Accept Host Keys", which allows host keys to be accepted automatically. Note: Enabling this option is not considered a security best practice.
  • SSH2: Added a session INI-file-only option "Ident String" that allows the SecureCRT identity string to be specified.
  • Added a "Close All Not Connected" item to the tabbed/tiled session right-click menu, which makes it easy to close all sessions that are not currently connected.
  • Added a menu item to the Zoom pull-right menu in the View menu that allows a session to be restored to its original size if it has been zoomed.
  • Added an option for disabling session zooming with keyboard shortcuts to the Global Options dialog.
  • Added support for Xterm OSC escape sequences to change background and foreground colors.
  • In the Session Manager and Connect dialog, it's now possible to connect a session or sessions in a new window without changing the option that specifies whether or not sessions should be opened in a tab.
  • The connection status icons were updated.
  • Mac/Linux: The button bar can now be positioned at the top of the SecureCRT window.
  • Changes:
  • By default, SecureCRT now listens for port forward requests only on 127.0.0.1.
  • Improved the drawing performance of keyword highlighting.
  • Quick Connect sessions that are saved are put in the current folder in the Session Manager.
  • Added a keyboard shortcut for the "Reconnect All" menu item.
  • The ability to use a session as a firewall has been added to the Quick Connect dialog and the Session wizard.
  • The escape sequence "CSI ?3l" is ignored when the SecureCRT window is maximized or full screen.
  • Added the ability to map a key or button to display the Global or Session Options dialogs.
  • In the Session Manager, when a folder or multiple sessions are selected, selecting the new menu item "Connect in Tabs in New Window" opens the selected sessions in tabs in a new SecureCRT window.
  • Changed the SSL GUI protocol name to "Telnet/TLS" to reflect that TLS is supported.
  • Added "Contact Support" to the Help menu.
  • SSH2: If host key authentication fails with the ssh-dss algorithm, the ssh-rsa algorithm is preferred on subsequent attempts to reconnect the session.
  • SSH2: It's now possible to specify the minimum group exchange prime size in the Session Options dialog.
  • SSH2: SecureCRT can now connect to Cisco devices that send the incorrect identity string "SSH-2.99-Cisco-1.25".
  • SSH2: The "diffie-hellman" key exchange algorithm is off for the default session. This change only affects new installations.
  • SSH2: SHA-1 and SHA-2 fingerprints are displayed for public keys in addition to MD5.
  • SSH2: In all places where the host key fingerprint is displayed, the SHA-2 fingerprint is also displayed.
  • Mac: The font dialog now shows only fixed-width fonts that can be used with SecureCRT.
  • Mac: Improved the docking interface for the Session Manager.
  • Mac/Linux: If the option "Open Sessions in a Tab" was disabled in the Session Manager and the sessions in a folder were connected using "Connect in Tabs", all subsequent sessions were opened as tabs in the same window.
  • Bug fixes:
  • Attempting to delete a session without a name caused every session in the session database to be deleted.
  • If SecureCRT had insufficient permissions to access a configuration folder located on OneDrive, SecureCRT crashed.
  • SecureCRT could become unresponsive when settings were being imported or exported, especially when the configuration was large (e.g., lots of sessions).
  • SecureCRT could hang or display output incorrectly when the output contained OSC RGB color substitution escape sequences.
  • When upgrading from a version of SecureCRT prior to 6.1, session logon actions were not migrated.
  • In the Quick Connect dialog, if all authentication methods were disabled for SSH2 and then an attempt was made to change the protocol to Telnet, a warning was displayed and the protocol was not changed.
  • When the session options "Shift forces local mouse operations" and "Send scroll wheel events to remote" were set, scroll wheel events with SHIFT pressed were sent to the remote system.
  • It was not possible to drag the file separator in vim.
  • The selection in a session could be lost when switching between tabbed sessions or when the cursor was repositioned to the same row as the selection.
  • If the Session Manager had "Auto Hide" set and focus was in an application other than SecureCRT, if the mouse was moved over the Session Manager, it appeared to be activated, but clicking in the Session Manager did nothing.
  • If the global options "Reuse disconnected tabs" and "Connect sessions in tabs" were off and the SecureCRT window contained a disconnected tab, when a new session was connected, it was opened in a new tab.
  • A highlight keyword list with the name "New..." could not be edited or deleted. The name "New..." is no longer allowed.
  • If a disconnected tab was reused and the new session had a different value specified for the scrollback lines, the value from the old session was used.
  • When the narrow font was being used, pressing the "Font" button for the Normal font showed the wrong font in the Font dialog.
  • SecureCRT did not produce the correct result for the vttest test "Test of autowrap, mixing control and print characters."
  • If SecureCRT started in tiled mode and then was switched to tabbed mode, the "Show button bar" session option was not honored.
  • If the windows transparency settings were change to values other than 255 (opaque), the settings were not honored when SecureCRT restarted.
  • Pass-through printing did not print Unicode characters correctly.
  • SSH2: If the host key database was on an offline cached network drive, SecureCRT was not able to save new host keys.
  • SSH2: The cached session password was not updated after a password change was forced by the remote system.
  • SSH2: The SHA-2 fingerprint of the public key was not correct when a .pfx file was used as the public key.
  • SSH2: When attempting to connect to a session that specified PKCS #11 public-key authentication using the ActivClient DLL, the connection failed due to an error creating the signature during public-key authentication.
  • Mac: If multiple tabbed sessions were connected and one of the sessions was scrolled back, when switching between the tabs, part of the terminal window could be missing.
  • Mac: COMMAND+V could not be used to paste into dialogs.
  • Mac: Local shell sessions opened in a tab when the "Open in a tab" setting was off.
  • Mac: If SecureCRT was in full-screen mode and three sessions were connected, the wrong menu was displayed when the center tab was right clicked.
  • Mac: When using an Apple Magic Mouse, doing a side-swipe on the mouse after or while double clicking caused focus to be put in the Session Manager.
  • Mac: If the SecureCRT window was maximized after connecting to a session and the toolbar was hidden, the SecureCRT window resized and changed position. Then if the SecureCRT was maximized again and the same session was connected again or closed, the SecureCRT window resized and changed position again.
  • Mac: If the SecureCRT application window was closed, nothing happened when "Import Settings..." or "Export Settings..." was selected from the Tools menu.
  • Mac/Linux: When connecting to an SSH2 server with "ssh1" in the hostname, the host key was prompted for even if it had been accepted.
  • Mac/Linux: The Session Manager could not be docked by double- clicking its title bar.
  • Mac/Linux: When focus was in the Command window, and the shortcut key ALT+ was entered, the number was sent to the Command window and the specified tab was not activated.
  • Mac/Linux: If multiple sessions were open in tabs and one tab had some text selected and the other tab was activated, the selection in the original tab was lost.
  • Mac/Linux: If multiple sessions were selected in the Session Manager or Connect dialog, using the context menu could change the selection to contain only a single session.

New in SecureCRT 7.3.6 Build 963 (Dec 2, 2015)

  • Bug fixes:
  • The New Session wizard reported an error when an IPv6 address wasentered as the hostname.
  • If the option "Show command window" was modified for the activesession from the Session Options dialog, it did not take effectuntil the session was closed and re-opened.
  • When first switching from tiled to tabbed sessions, the sessionoption "Show command window" was not honored.
  • If the command window was turned off while SecureCRT was in tiledmode and the application window was maximized, the sessions werenot re-tiled automatically.
  • When the global option "Default transfer type" was set to "Promptfor type," the option "Use this type for all files" was enabled.
  • SSH2: SecureCRT hung when attempting to connect to a session thatused CAPI for public-key authentication if the personal store wasempty.
  • Mac: SecureCRT crashed when attempting to do public-keyauthentication with a certificate in a format not supported bySecureCRT.
  • Mac: If a password for a session was saved in the OS X keychainand then the option to save to the keychain was turned off, whenconnecting to the session, the authentication prompt contained anincorrect password.
  • Mac: On OS X 10.11 (El Capitan), there were display issues withthe San Francisco system font.

New in SecureCRT 7.3.5 Build 903 (Sep 10, 2015)

  • Bug fixes:
  • An error was reported if a host was specified on the command line using an IPv6 address.
  • If a key was mapped to a key on the number pad and NUM LOCK was on, the mapped key did not honor the NUM LOCK setting.
  • Mac: On Yosemite (OS X 10.10), SecureCRT crashed at startup if the global settings contained an invalid value for the application window position or size.
  • Mac: If the option to reuse tabs was set and a tabbed session was disconnected and then another session was connected from the Session Manager, focus did not move into the session.
  • Mac/Linux: If the toolbar was unchecked in the View menu, it was displayed the next time SecureCRT started.

New in SecureCRT 7.3.4 Build 839 (Jun 17, 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 SecureCRT 7.3.3 Build 779 (Apr 1, 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 SecureCRT 7.3.2 Build 752 (Feb 27, 2015)

  • Changes:
  • The escape sequence ESC E (DECNEL, next line) is treated like a CR (or CRLF) so that the command on that line gets logged.
  • SSH2: When attempting to authenticate using a CAPI key or certificate with a smart card, if the card returns an error, SecureCRT attempts to continue authentication, which allows authentication to succeed with certain smart cards, such as GoldKey.
  • Bug fixes:
  • SecureCRT crashed when attempting to run a Perl script using ActiveState ActivePerl 5.18 and 5.20. SecureCRT still cannot run the script. Switching ActivePerl 5.16 is recommended.
  • When the global option "Save window state for each session" was set and SecureCRT was in full-screen mode, if a local shell session was opened or a session was cloned, SecureCRT went out of full-screen mode.
  • If autohide was on for the session manager, the most recently opened session was not selected when the session manager was shown again.
  • If a keymap was modified through a script, it was not always reloaded.
  • When using the Connect dialog, if a session with saved credentials was connected by double clicking, extraneous text appeared in the session window before the prompt.
  • Telnet: When connected to a session with a character or line send delay specified, the delay was not honored when a script sent a string.
  • Windows: On Windows 8.1, SecureCRT crashed if TAPI was selected as the protocol in the Quick Connect dialog and the Configure button was pressed.
  • Mac/Linux: If a local shell session was started from an alias, it was not possible to interrupt output using CTRL+C.
  • Mac/Linux: If the global option "Show horizontal scroll bar" was set and the connected session had the session options "Show horizontal scroll bar" and "Synchronize view to size" set, after performing a long directory list that filled the screen, the last row had extra space below it.
  • Mac/Linux: The crash reporter dialog did not show crash information for the most recent crash.

New in SecureCRT 7.3.1 Build 685 (Dec 5, 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.
  • 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 SecureCRT 7.3.0 Build 657 (Oct 24, 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.

New in SecureCRT 7.3.0 Build 633 Beta 4 (Sep 24, 2014)

  • Changes:
  • The maximum length for a regular expression for keyword highlighting was increased to 256 characters.
  • Substitution paramters such as ${VDS_INSTALL_PATH} can be used in a script filename.
  • Mac: Since the minimize and zoom buttons were always grayed out, they are hidden when SecureCRT is used with the Moom session manager.
  • Bug fixes:
  • If a regular expression that caused everything to be highlighted was specified for a session and the session window was made narrow enough for command output to wrap, some words did not get highlighted.
  • If the width of the session manager was resized while it was in autohide mode, the new width was not saved when SecureCRT exited.
  • If autohide mode was on for the session manager, then the session manager was closed and reopened and autohide was turned off, changing any value in the Session Options dialog caused autohide to be turned back on.
  • In the Keyword List Properties dialog, if a keyword was selected when a new word was added, pressing the "Set Color" button and selecting a color caused the previously selected and new keyword to be changed.
  • In the Keyword List Properties dialog, after changing the color for a keyword, the keyword was not highlighted in the keyword list.
  • Mac: If the Connect dialog was used instead of the Session Manager, using the keyboard shortcut COMMAND+I to move focus to the session filter box caused SecureCRT to crash.

New in SecureCRT 7.3.0 Build 622 Beta 3 (Sep 10, 2014)

  • New features:
  • Added a search filter to the Connect dialog, which helps find sessions quickly, especially when a large number of sessions have been saved.
  • Changes:
  • The logic used for matching word delimiters was improved so that keyword and regular expressions (Windows only) that contain word delimiters do not affect keywords and regular expressions that do not contain word delimiters.
  • The order of keywords can now be specified for keyword highlighting.
  • SSH2: The modulus for the Diffie-Hellman key exchange algorithms can be set from 1024 to 8192.
  • Bug fixes:
  • Saved passwords could be deleted inadvertently by pressing ENTER when focus was in the Password field of the Password Properties dialog.
  • When using the filter bar to search for sessions, the session tree did not return to the original state if the option "Save expanded folder state in connect dialog" was off.
  • Mac: The keyboard shortcut COMMAND+N opened a new window when "Open in a tab" was selected.

New in SecureCRT 7.3.0 Build 611 Beta 2 (Sep 5, 2014)

  • Changes:
  • ANSI emulation now supports the CHA sequence (CSI pn G).
  • The keyboard shortcut CTRL+A can be used to select all text in the Send String field in the Map Button dialog.
  • In the session manager, when text is entered in the filter bar, the first matching session gets selected.
  • Bug fixes:
  • Mac: SecureCRT could crash when sessions were dragged between application windows.
  • Mac: SecureCRT crashed if focus was in the filter bar and SecureCRT was closed using CMD+Q.
  • Mac: If a three-finger swipe was used to select text in the terminal window and then CMD+V was used to paste, the wrong text was pasted or pasting was very slow.
  • Mac: Attempting to convert a private key to OpenSSH format failed to export the key.
  • Mac: If there was text in the clipboard and the Find dialog was accessed using CMD+F, pressing CMD+V caused the text to be pasted in the terminal session rather than the Find dialog.
  • Mac/Linux: In the session manager, if the filter bar was cleared after being used to filter sessions, the session tree was not restored to its original state.
  • Mac/Linux: Focus could be incorrectly taken out of the connect bar when the session manager was automatically hidden.
  • Mac/Linux: The Export Settings and Import Settings dialogs did not automatically scroll when the progress information was displayed.

New in SecureCRT 7.2.6 Build 606 (Aug 20, 2014)

  • Bug fixes:
  • 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 SecureCRT 7.3.0 Beta 1 (Aug 8, 2014)

  • New features:
  • Added the ability to specify colors for keyword highlighting.
  • In keyword highlighting, the styles (reverse video, bold, and color) can be combined.
  • Added the ability to edit keywords used for keyword highlighting.
  • Added support for exporting and importing SecureCRT settings to and from XML, which makes it easier to copy settings from one machine to another.
  • Mac/Linux: Added a session manager that can be used in place of the modal Connect dialog. The session manager can be in a pane in the SecureCRT window or can be an undocked modeless dialog.
  • Added a search filter to the session manager, which helps find sessions quickly, especially when a large number of sessions have been saved.
  • Added the ability to connect to a remote system through a named pipe.
  • Added the ability to script Kermit file transfers.
  • Added the ability to specify the substitution parameter %USERNAME% as a session username.
  • Added a new session option "Position cursor on left click" that allows the mouse to move the cursor to a different location.
  • Added a new session option "Enable alternate screen switching".
  • Added an option to disable the hover text for buttons on the button bar.
  • Added a new menu item "Close All Sessions" to the tab menu, which allows all sessions to be closed without closing the SecureCRT window.
  • Added a new global option "Exit SecureCRT when last session is closed" that specifies whether or not the SecureCRT window should be closed when the last session is closed.
  • Added a global option to swap ENTER and CTRL+ENTER in the command (chat) window.
  • Added the ability for the command (chat) window to be controlled independently in each SecureCRT window.
  • Mac: Added support for Finder tags.
  • Changes:
  • Added the ability to store keys larger than 2048 bits in agent.
  • Added the ability to generate keys larger than 2048 bits.
  • When connecting a session, if there's an agent key associated with the session, it is tried first. This can help prevent a session from failing to connect because the maximum number of authentication retries was exceeded.
  • The MD5 and SHA-1 fingerprints are now displayed in dialogs that show host key information.
  • When multiple sessions are being edited, if a single expect or send string is changed in the session automated logon option, only the single string is changed in all the sessions. Previously, the entire expect/send block was written to the sessions.
  • Added the ability to send a disconnected session to a new window.
  • Log files are saved with a .log extension by default unless a different extension is specified.
  • Font information was added to the information stored in the personal data folder.
  • Mac: The folder used when a key or button is mapped to MENU_LOG_SESSION is the same as the folder used when "Log Session" is selected from the File menu.
  • Bug fixes:
  • SecureCRT could crash if multiple sessions specified the same session as a firewall (i.e., jump host).
  • SecureCRT could crash when the send delay "Prompt" option was set and a large amount of text was pasted into a session.
  • SecureCRT could crash when several GNS3 sessions were connected in rapid succession.
  • SecureCRT could hang if a partial execute escape sequence was received.
  • When using mcedit (Midnight Commander editor), incorrect text was selected when switching between multiple screens or if the SHIFT key was down and the mouse moved, which caused incorrect text to be pasted.
  • If a session was resized and then another session was opened, the application window was changed to the size before the session was resized.
  • When a color scheme that was being used by two or more open sessions was changed from the Session Options dialog, only the active tab was updated to reflect the change.
  • If a button was mapped to the menu function CLEAR_SCREEN_AND_SCROLLBACK, if the SHIFT key was held while the button was clicked, only the current session was cleared.
  • If the system resolution was changed while SecureCRT was running, the font information in the Session Options dialog did not get updated.
  • TAPI: If sessions were copied from one machine to another and the the modem in the TAPI sessions did not exist, SecureCRT did not indicate that there was a problem when the session was edited and displayed a cryptic error when attempting to connect.
  • Mac/Linux: SecureCRT could hang or cause 100% CPU usage when the terminal protocol was changed.
  • Mac/Linux: If the posix directory was a symbolic link, it caused SecureCRT to hang when attempting to open the Session Options dialog.
  • Mac/Linux: When specifying a log file for a session, if the filter was set to "*.txt", a ".log" extension was used instead.
  • Mac/Linux: If SecureCRT and SecureFX were running and a change was made to the global or session options in one of the applications, the changes were not picked up by the other application.

New in SecureCRT 7.2.5 Build 550 (Jun 6, 2014)

  • 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 SecureCRT 7.2.4 Build 524 (May 2, 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 SecureCRT 7.2.3 Build 500 (Apr 2, 2014)

  • Bug fixes:
  • 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.
  • 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 SecureCRT 7.2.1 Build 443 (Jan 18, 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 SecureCRT 7.2.0 Build 415 (Dec 13, 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 SecureCRT 7.2.0 Build 407 Beta 5 (Dec 6, 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.
  • Windows: 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.
  • Windows: If the session manager was docked in the bottom pane next to the command window, the title bar was displayed in the command window.
  • Windows: If the session manager was docked next to the command window, it's position was not stored correctly when SecureCRT exited.

New in SecureCRT 7.1.3 Build 378 (Nov 11, 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 SecureCRT 7.2.0 Build 384 Beta 3 (Nov 6, 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 SecureCRT 7.2.0 Build 359 Beta 1 (Oct 9, 2013)

  • New features:
  • Windows: Added a Session Manager that can be used in place of the modal Connect dialog. The Session Manager can be in a pane in the SecureCRT window or can be an undocked modeless dialog.
  • Added a global option to store personal data such as usernames and passwords in a location separate from the rest of the session data, which allows personal data to be kept private while other configuration data is stored on a network drive or on the cloud so that it can be used on different systems or shared with colleagues.
  • Windows/Mac: Added the ability to zoom a session (increase or decrease the font size) using CTRL+ or CTRL+"+" or CTRL+"-".
  • Added a script object CommandWindow that provides access to the command (chat) window from a script.
  • Added Ymodem support to the FileTransfer script object, which allows Ymodem transfers to be scripted.
  • The script function Screen.Send() can be used to send text to the screen only by using a new optional parameter.
  • Added the ability to pass arguments to logon scripts.
  • Added a two-digit year log file parameter substitution "%y".
  • Added a session INI-file-only option "Ignore Shift Out Sequence" that prevents SecureCRT from going into graphics mode when Shift Out (\016) is received.
  • SSH2: Added support for SHA-2 MAC algorithms.
  • SSH1/SSH2: Added two new session INI-file-options "Use Global Host Key Algorithms" and "Host Key Algorithms" that allow the session to order and filter the global host key algorithms. The session host key algorithm list must be a subset of the global host key algorithm list.
  • Mac/Linux: Added a new session option "Draw lines graphically" that improves the appearance of line-drawing characters.
  • Changes:
  • The "chat window" has been renamed to "command window".
  • The option to open sessions in a tab is on by default.
  • SecureCRT uses the Default session's background color as the background color of the application window at startup.
  • For Ymodem and Zmodem uploads, files are removed from the file list after they are successfully transferred.
  • The anti-idle options to send a string or protocol NO-OP can now be configured to an interval of less than 10 seconds.
  • The Xterm keymap now sends Esc[H and Esc[F for Home and End.
  • Pressing SHIFT+TAB sends "^[[Z" to the session when Xterm emulation is specified.
  • The user interface reflects that when the global option "Use trackable insertion caret" is set, the session option "Cursor style" must be set to "Vertical Bar".
  • SSH1/SSH2: Added the session option "Force session channel to close on disconnect" to the Session Options dialog.
  • Telnet: Added the option "Server requires bare CR" to the Connection/Telnet category in the Session Options dialog.
  • Serial: The default flow control was changed to none. This only affects new installations.
  • Bug fixes:
  • If a new session was created and the password was saved, the password had to be re-entered if the session was connected again without disconnecting the original session.
  • If authentication prompts were displayed in the terminal window, the Screen.Synchronous property did not work correctly.
  • If a tab was renamed manually, it reverted back to the original name after toggling between tabbed and tiled mode or if the session received an OSC_TITLE sequence from the remote system.
  • The Transfer menu was available during a transfer.
  • The "Send Zmodem" menu item was available on the drag and drop transfer menu when a folder was dragged.
  • SSH2: If the host specified for GSSAPI authentication was an IP address, SecureCRT hung during kexinit.
  • Windows: The vertical scrollbar in SecureCRT sessions did not work with Windows 8 and WindowBlinds.
  • Windows: If a connected session specified the "Windows" color scheme and the system colors were changed, the session did not reflect the system changes.
  • Mac/Linux: It was not possible to map keys or buttons to script recording menu items.
  • Mac/Linux: If a session name included an ampersand character ("&"), the ampersand did not appear in the session name in the recent session list.
  • Mac: The global INI-file-only option "Close Button On Tabs" was not being honored.

New in SecureCRT 7.1.2 Build 316 (Aug 9, 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 SecureCRT 7.1.1 Build 264 (May 31, 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.
  • 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.

New in SecureCRT 7.1.0 Build 244 (May 3, 2013)

  • Bug fixes:
  • If a connected session was cloned and the terminal protocol of the cloned session was changed and then the original session was cloned again, SecureCRT crashed.

New in SecureCRT 7.1.0 Build 238 Beta 5 (Apr 26, 2013)

  • Changes:
  • Mac: The permissions on the installer have been modified so that users other than the one who installed the application can run it.
  • Mac: Improved the look of the button bar on the Retina display.
  • Bug fixes:
  • SSH2: If an SFTP connection failed due to an "open channel" error, the SFTP tab incorrectly showed the connection status as connected.
  • Mac: If an application had been installed and then uncleanly uninstalled, SecureCRT crashed on startup.
  • Mac/Linux: If the session option "Synchronize view to size" was set and the SecureCRT window was maximized and the font was small enough so that more than the maximum number of columns could fit in the terminal window, SecureCRT crashed.

New in SecureCRT 7.1.0 Build 230 Beta 4 (Apr 12, 2013)

  • Changes:
  • Added support for the Cursor Horizontal Absolute (CHA) escape code to the VT100 and ANSI emulations.
  • Mac: Improved the look of the toolbar icons on the Retina display.
  • Bug fixes:
  • SecureCRT could crash if CTRL+TAB was used to cycle through the tabbed sessions and then the sessions were closed using CTRL+F4 without ever releasing the CTRL key.
  • If the global option "CTRL+TAB switches to most recently used tabbed or tiled session" was set, the application window title did not get updated when a session tab was closed and a different session become the active tab.
  • Windows: SecureCRT crashed after "+++" was typed into a TAPI session.

New in SecureCRT 7.0.4 Build 537 (Apr 5, 2013)

  • Bug fixes:
  • SecureCRT could crash if an SFTP tab was performing a transfer and the tabbed session that launched the SFTP tab was closed.
  • If several tabbed sessions were connected and CTRL+TAB was used to cycle through them, the tab contents were not always updated.
  • If a session could not be cloned because the channel connection failed, the cloned session's tab title was blank.
  • SSH2: If a session specified a remote SFTP directory that contained an invalid character, such as "~", SecureCRT crashed when attemping to connect the SFTP tab.
  • Windows: On Windows XP, if a session specified more than 140 local forwards, when the session connected, the forwards above the 140th failed.
  • Mac: If a session had the "Scale the font" resize option set and SecureCRT was maximized, the last line was not visible.

New in SecureCRT 7.1.0 Build 219 Beta 3 (Mar 29, 2013)

  • Bug fixes:
  • When a dependent firewall session's option "Display logon prompts in terminal window" was set, the parent session's username was used instead when the dependent firewall session connected.
  • When a dependent firewall session connected, the dependent session's specified authentication method was not used.
  • Windows: If a session was logging to a file and then logging was stopped, the log file's parent folder could not be renamed or deleted.
  • Windows: If the administrative option to disallow saving passwords was set and a password was specified on the command line, it was not used.
  • Mac: The connection status icon and session name overlapped in the session tab when there was not enough room to display both.

New in SecureCRT 7.1.0 Build 208 Beta 2 (Mar 15, 2013)

  • Changes:
  • When the "Scroll to bottom on output" session option is off, the session never scrolls to the bottom. Previously, if less than a screen was scrolled back, the session always scrolled to the bottom on new output.
  • Added support for extended packets in Kermit, which allows ASCII files to be transferred and improves transfer performance.
  • Line drawing for Korean language fonts was improved.
  • A session using VT220 emulation ignores DEL characters received from the remote system.
  • If the global option "CTRL+TAB switches to most recently used tab" is set, when a tabbed session is closed, focus goes to the previously active tab instead of the most recently opened tab.
  • Bug fixes:
  • Scripts that attempted to connect an ad hoc session using a protocol flag such as "/SSH2" reported the following error: The default session is not valid with the "/S" command-line flag.
  • If the font of a connected session was changed, the session's rows and columns were not adjusted.
  • When the SecureCRT window regained focus, an extra mouse click was required before being able to select text.
  • The authentication prompt was displayed every time a host disconnected and reconnected, which resulted in multiple authentication prompts being displayed when authentication timed out.
  • When SecureCRT was integrated with SecureFX, if a dependent session firewall was specified and then the session protocol was changed, the firewall field did not get updated on the protocol page.
  • Mac: After several days of constant use, especially with a lot of switching into and out of full screen mode, the toolbar could disappear.
  • Mac: The Connect bar disappeared after going into and out of full screen mode.
  • Mac: The minimum tab width global option was not honored.

New in SecureCRT 7.1.0 Build 195 Beta (Feb 27, 2013)

  • New features:
  • On Mac and Linux, added the ability to tile sessions within the SecureCRT application window. Sessions can be tiled or cascaded. Scripts can use the "Tab" object to work with tiled sessions.
  • Added support for dependent sessions so that a connection can be made to a jump host or SSH gateway before the session is connected.
  • Added support for the Kermit file transfer protocol. Binary and ASCII transfers are supported.
  • SSH2 on Windows: Added support for SHA1 in RSA signatures, which allows X.509 certificates to be used in FIPS mode and other settings where MD5 cannot be used.
  • A button action can be sent to all connected tabbed or tiled sessions by pressing SHIFT+ on the button.
  • Added a character send delay option to wait for a text prompt.
  • Added a new logging substitution variable "%P", which inserts the session's port.
  • Added the ability to copy ANSI text to the clipboard, which allows attributes such as color and font to be preserved on the clipboard.
  • Added support for sending Xterminal escape sequences for CTRL+ keys.
  • Added the ability to specify ANSI colors for individual sessions in addition to the global option.
  • Windows: Added support for the Wyse label line.
  • Linux: Added support for printing.
  • Changes:
  • Improved scrolling performance when the session options "Jump scroll" and "Minimize drawing" are set.
  • Changed the protocol NO-OP to send decimal code 241 instead of 0.
  • When the escape sequence "CSI ?3l" is received, the data is added to the scrollback buffer before the screen is cleared.
  • Mac: The default font is now 11-point Menlo. This change only affects new installations.
  • Bug fixes:
  • SecureCRT could crash when attempting to clone a session connected to a device that does not support multiple connections if prompts for both sessions were displayed at the same time.
  • If a tab was manually closed and then was closed by a script, SecureCRT crashed.
  • SecureCRT could crash if it was tunneling through a SOCKS proxy on a laptop and the laptop was closed.
  • The password prompt was displayed every time a host disconnected, due to the session timing out, and reconnected automatically.
  • The cursor went below the session window if the chat window was displayed and the number of session rows was larger than the session window height.
  • If a machine had two monitors and the main SecureCRT window was dragged to the second monitor and maximized, when a session with the inital position located on the first monitor was opened and switched to fullscreen mode, the main window got moved to the first monitor.
  • In the "Connect" dialog, if a new folder was given the same name as an existing folder except for different capitalization, after exiting and restarting SecureCRT, both folders were gone.
  • If a key was mapped to VT_KEYPAD_ENTER, the key did not work when the terminal was in newline substitution mode.
  • SSH2: The global option "Cache session password" was not honored for keyboard interactive authentication.
  • SSH2: If a session was configured to use password and X.509 public-key authentication, if the key was signed, but failed, the same key was sent again instead of sending the next key.
  • Windows: If a terminal session channel could not be opened because of a resource shortage, an error was displayed and the terminal area was not displayed correctly.
  • Windows: The application icon was not removed from the Program group during an uninstall.
  • Windows: If "Connect" was selected from the Activator and "Quick Connect" was selected from the "Connect" dialog, the connection was not made.
  • Mac, Linux: Copying text from an RDP session caused SecureCRT to hang.
  • Mac: SHIFT and CONTROL keys did not work with the Chinese input methods sougou and QIM.
  • Mac: When Romaji was the selected language Input Source, the CONTROL key behaved like the COMMAND key.
  • Mac: When "Make Alias" was used to create a desktop shortcut, if the shortcut name contained a ".", the shortcut did not work.
  • Mac: When a Telnet connection failed, a "Broken pipe" error was displayed.

New in SecureCRT 7.0.3 Build 480 (Jan 18, 2013)

  • Bug fixes:
  • 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 SecureCRT 7.0.2 Build 418 (Oct 26, 2012)

  • Changes:
  • Mac: The look of text on Retina displays was improved.
  • Linux: Character encodings that cannot be used by SecureCRT are no longer shown in Terminal/Appearance category in the Session Options dialog.
  • Bug fixes:
  • If the protocol type was changed during authentication, SecureCRT crashed.
  • If a session's emulation was set to "Dumb", it continued to used dumb emulation after being changed to use a different emulation.
  • If a session reconnected automatically in the background when a different session's tab had focus, the title bar was updated to display the reconnected session name.
  • Windows: If a laptop was docked such that a secondary monitor was used and then SecureCRT was moved to that monitor and closed, when the laptop was disconnected from the dock and SecureCRT was restarted, it was visible in the task bar, but not on the laptop display.
  • Windows: On a system that had two monitors with the primary monitor having a larger display resolution than the secondary monitor, when SecureCRT was maximized on the primary monitor and then restored, it used the resolution of the secondary monitor.
  • Windows: When the sessions were tiled, if the main window was resized, some of the tiled windows did not send a screen resize to the remote system.
  • Mac/Linux: SecureCRT crashed after the Report button was pressed in the crash handler dialog.
  • Mac/Linux: If data was being output and the scrollbar was used to look at data in the scrollback buffer, the output was not paused.
  • Mac: Passwords specified on the command line were ignored if the global option "Use Keychain" was set.
  • Mac: If the global option "Show confirm disconnect dialog" was set and multiple SecureCRT windows with connected sessions were open and then one window was closed, attempting to switch between the remaining windows using COMMAND+` did not work.
  • Mac: When SecureCRT was not set as the default Telnet handler and the default Telnet handler check was on, a message was displayed every time SecureCRT went into or out of "Full Screen" mode.
  • Linux: Error text was not displayed correctly on Ubuntu with the Korean language pack installed and set as the primary language.

New in SecureCRT 7.0.1 Build 374 (Aug 30, 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 SecureCRT 7.0 Build 326 (Jul 4, 2012)

  • Bug fixes:
  • SSH1/SSH2: When a window decoration such as the chat window or button bar was toggled, or the Session or Global Options dialog was closed, IPv6 listening ports being used for tunneling were closed.
  • Mac/Linux: If the tab status indicators were set to "Colored rectangles", SecureCRT crashed when trying to lock a tabbed session.

New in SecureCRT 7.0 Build 318 Beta 4 (Jun 20, 2012)

  • Bug fixes:
  • If a script issued an "exit" command to an SFTP session, SecureCRT crashed.
  • If a script issued an "ls" command to an SFTP session, SecureCRT hung.
  • When multiple tabs were open, sometimes the leftmost tab was shifted over such that the status indicator icon was partially obscured.
  • When multiple tabs were open, if a tabbed session was closed, the tab to the left of the closed tab was activated instead of the tab to the right.

New in SecureCRT 7.0 Build 307 Beta 3 (Jun 6, 2012)

  • Changes:
  • Windows: The "Window" menu was changed so that it always contains the following items: Tabs, Tile Vertically, Tile Horizontally, Cascade, and the list of open sessions.
  • Windows: If the sessions are tiled and a new session is opened, all the sessions are automatically re-tiled.
  • Windows: When a tiled session is closed, the remaining sessions are automatically re-tiled.
  • Windows: When the sessions are tiled and the SecureCRT window is re-sized, the sessions are automatically re-tiled.
  • Bug fixes:
  • Authentication banners were sometimes displayed at the logon prompt.
  • Unicode and combining characters (Korean in particular) were sometimes rendered incorrectly.
  • SecureCRT failed to clear all tabstops when the escape sequence to clear all tabstops was processed.
  • Windows: SecureCRT could hang when used in a Webex session.
  • Windows: After SecureCRT had been sitting idle for many hours, the interface could become unresponsive.
  • Windows: SecureCRT could crash if the application window was resized a lot or a lot of tab switching was done.
  • Windows: SecureCRT crashed when attempting to record a script if no sessions were open.
  • Windows: SecureCRT crashed if a script was launched from a button or mapped key and no sessions were open.
  • Windows: If a mapped key or button used "\v" to paste clipboard data, the data pasted was not correct.
  • Windows: If a session had the "Scale the font" option set, when switching between tabbed and tiled sessions, that session's font could become extremely large.
  • Windows: The tab titles of cloned sessions did not contain the number indicator (e.g., "(1)", "(2)", etc.).
  • Mac: If the left margin was increased, selections were offset by the amount of the margin.
  • Mac: After using COMMAND+W to close SecureCRT, it could not be launched from the dock icon.

New in SecureCRT 7.0 Build 281 Beta 1 (May 5, 2012)

  • New features:
  • Added the ability to start a built-in TFTP server when a session connects.
  • SSH2: Added the ability to skip authentication methods while authenticating.
  • When the mouse hovers over a button, the command the button is mapped to is shown as hover text.
  • Added the ability to map the items on the "Tools" menu to a button or key.
  • Added the ability to map "Always on Top" to a key.
  • Added support for the "Insert" key to the Wyse 50/60 emulation.
  • Changes:
  • Improved the performance of the "Connect" dialog when the configuration is located on the network.
  • It is now possible to close the last tab.
  • The port can now be specified in the "Connect" bar on the toolbar.
  • The chat window history limit has been increased to 32,000 commands.
  • When scrolling back into the scrollback buffer, empty lines (such as from the "clear" command) are not shown.
  • Added a way to access buttons that were not visible on the button bar if the configured buttons did not fit in the window.
  • Added "Send Break" to the "Edit" menu, which sends a Telnet break.
  • If a change is made to the settings of a cloned session, the change is propagated to the other SecureCRT windows and/or sessions.
  • The first tabbed session's scrollbar settings are used for subsequent tabbed sessions so that all the sessions will have the same number of rows and columns.
  • When attempting to use Zmodem to transfer a file larger than 4 GB, an error is reported.
  • The installer now remembers the installation options from the previous install.
  • Kerberos delegation results are displayed in the trace output.
  • The script file location is displayed when a script cannot be opened.
  • The "Connect" dialog now has the same icons as the toolbar.
  • Changed the button labels on the dialog that is displayed when the default session is changed in order to make it harder to accidentally apply the changes to all sessions.
  • Telnet: When the session's IP address is IP4, it is displayed in the status bar.
  • Mac: Added the ability for SecureCRT to update changed passwords in the Mac Keychain.
  • Mac: If a tabbed session is moved out of a SecureCRT window that only contains the one session, the application window is closed.
  • Mac: The keyboard shortcut for printing is now COMMAND+P.
  • Mac: The COMMAND key can now be used to select multiple sessions in the "Connect" dialog.
  • Bug fixes:
  • SecureCRT crashed when a script was run that sent an exit command to an SFTP tab.
  • SecureCRT crashed if a script called GetOption("[SSH2] Port") on a session that did not specify a firewall.
  • If a command was typed at the prompt, but ENTER was not pressed, and then the session was scrolled back to the oldest row and the top row was selected and ENTER was pressed, SecureCRT could crash.
  • SecureCRT crashed when the "Retain size and font" session option was set, the lines of scrollback was set to 0, the visible rows were less than the actual number of rows, the first several rows were not visible, and an escape sequence that erased a line was sent.
  • Xmodem transfers could hang at the beginning of the transfer.
  • If a host key hostname contained an escaped ".", it could not be saved.
  • When using mouse mode in vi, vim, or mc, there was a slight delay between clicking the mouse and the cursor being positioned at the mouse location.
  • When scripting was administratively prohibited, the "Script" menu was still available.
  • When the global option "Reuse disconnected tabs" was set and a session that had the "Show chat window" and "Sync view to size" options set was disconnected and then a session with "Sync view to size" enabled, but "Show chat window" disabled was connected, the number of rows in the session was not correct.
  • When a key was mapped to a function or arrow key that sent a multi-byte escape sequence, the mapped key sometimes didn't work.
  • The title bar setting in the "Default" session could be used to rename tabs using substitution parameters for "Quick Connect" sessions, but was not honored for saved sessions without a username.
  • The "Quick Connect" dialog sometimes used the default username or previously used username even though the username was empty.
  • The keyboard-interactive password prompt was displayed when the password was specified on the command line with the /PASSWORD flag.
  • If a log file contained a leading space, an error was reported.
  • The keyboard accelerator for "Clear Screen and Scrollback" did not work from a custom menu.
  • If there were two tabbed sessions and there was scrollback data in the second tab and then the second tab was disconnected and reused for a different session, the scrollback was not cleared.
  • When Zmodem was used to transfer a file larger than 2 GB, the progress information was not correct.
  • If /Log was specified on the command line and additional parameters such as session name or username were also specified, the /Log parameter was not honored.
  • If Connect() was called from a script and the option to suppress popups was set, it was not possible to detect failures by looking at error codes in crt.GetLastError and crt.GetLastErrorMessage.
  • SSH1/SSH2: If key re-exchange occurred during a transfer and "[email protected]" compression was being used, the session disconnected.
  • SSH2: Authentication failed when the server requested the keyboard- interactive method more than once.
  • Mac: A new session tab could hang after being opened by a script.
  • Mac: The global option "Reuse disconnected tabs" was not being honored.
  • Mac: Printing to a PDF file did not work.
  • Mac: Scrolling could cause stray pixels to be displayed in the session window.
  • Mac: When the 14-point Monaco font was used and the global option "Enable Font Smoothing" was off, some characters were cut off while being typed.
  • Mac: If the "Connect" dialog was resized so that it was partially below the dock, the next time it was opened, the top of the dialog was off the screen.
  • Mac: If the SecureCRT window was moved by the toolbar, it could get hidden behind the system menu.
  • Mac/Linux: When the toolbar was hidden, the "Connect" bar could still be accessed using shortcuts.

New in SecureCRT 6.7.5 Build 411 (Apr 21, 2012)

  • Bug fixes:
  • 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.
  • Mac/Linux: When a button was added to the button bar while a session was connected, the session size decreased.

New in SecureCRT 6.7.4 Build 354 (Feb 3, 2012)

  • Changes:
  • This version of SecureCRT is not compatible with older versionsof the Activator and older versions of SecureCRT are notcompatible with this version of the Activator.
  • Bug fixes:
  • SecureCRT could crash while idle when several Telnet sessionswere connected.
  • SecureCRT crashed if a tabbed session was disconnected while ascript was running.
  • The URL syntax of telnet: did not work.
  • If an attempt to run a script in a locked session was made,SecureCRT incorrectly reported that a script was already running.
  • Windows: On Windows 7, if a second binary transfer was attemptedafter the first binary transfer completed, nothing was transferred.
  • Windows: If the "SCRTMenuToolbarV2.ini" file was corrupted,SecureCRT crashed on startup with a Windows runtime error.
  • Mac: Keys mapped to MENU_WINDOW_NEXT and MENU_WINDOW_PREV werenot saved correctly.
  • Linux: On Ubuntu, SecureCRT crashed when attempting to establishan SSH2 connection to a local or remote host.
  • Linux: When Ubuntu ran on a system with an older processor, suchas Pentium 4 or Pentium M, SecureCRT crashed when attempting toconnect to a Secure Shell server.

New in SecureCRT 6.7.3 Build 292 (Nov 10, 2011)

  • New features:
  • Added support for Ubuntu Linux 11.10. 32-bit and 64-bit installers are available.
  • Added support for Red Hat Enterprise Linux 6.0. 32-bit and 64-bit installers are available.
  • Bug fixes:
  • If the default session was edited and the changes were written to all sessions, the logon actions were set to the default for all SSH2 sessions regardless of whether or not the logon actions had been changed.
  • If a script was running in a tabbed session and the tab was closed while the script was running, a script cancel error was reported.
  • With the "Show confirm disconnect dialog" option on, if a script was running and "Disconnect" was selected from the menu or toolbar and then the disconnect operation was cancelled, the script was stopped anyway.
  • Telnet: When CTRL+S was used to suspend output, the CPU usage went to 100%.
  • Mac/Linux: If the Public Key Assistant was used to generate a DSA key in OpenSSH key format and then upload the key file, the file had 0644 permissions instead of 0600 permissions, which meant that OpenSSH refused to use it.
  • Mac/Linux: If a license field, such as Name or Company Name, contained more than one line of text, the license was accepted, but could not be used when SecureCRT restarted.
  • Mac: On a system that previously had SecureCRT installed, after upgrading to OS X Lion, SecureCRT could not save license information.
  • Mac: On OS X Lion, the prompt for making SecureCRT the default Telnet application continued to be displayed when SecureCRT restarted after answering "Yes" to the prompt.
  • Mac: With the "Autoreconnect" option on, when a session connected through a forwarded port established by another session and a local session was also connected, if the sessions became disconnected, they did not reconnect automatically.
  • Linux: After exiting a local shell session, an I/O error was reported.
  • Linux: It was not possible to store passwords using the Password Properties dialog.

New in SecureCRT 6.7.2 Build 229 (Aug 12, 2011)

  • Xmodem transfers failed over connections using the Raw protocol.
  • The hostname was not saved in sessions that used the Raw protocol.
  • The item MENU_GOTO_CONNECT_BAR did not work when it was mapped to a button on the button bar.
  • The Connect dialog allowed connect attempts to sessions with the protocol set to "None".
  • The extend evaluation feature did not work correctly. After the offer was accepted, there was no button to extend the evaluation on the "Enter License" dialog as described in the instructions that had been e-mailed.
  • Telnet/RLogin: On Windows 7, when multiple sessions were running in different windows such that they were separate processes and command output was streaming in them, one or more of the connections could get reset.
  • Mac: If the system language was set to Russian, SecureCRT crashed when it was launched.
  • Mac: Mapping a button on the button bar to launch an application did not work.
  • Mac: After going into full screen mode and connecting to another session, the last line of the new session was cut off.
  • Mac: The "Public Key Wizard" dialog was taller than necessary.
  • Mac/Linux: It was not possible to double-click a port forward item in order to open its "Properties" dialog.

New in SecureCRT 6.7.1 Build 188 (Jun 17, 2011)

  • Changes:
  • Mac: When GSSAPI authentication is specified for a session, SecureCRT now looks for "libgssapi_krb5.dylib" in addition to "libgssapi.so".
  • Bug fixes:
  • If buttons were added to a new button bar and then an attempt was made to switch to a different button bar, SecureCRT could crash.
  • When Ymodem was used to transfer multiple files, only the first file was transferred correctly and sometimes the error "Invalid access to memory location" occurred.
  • In the Quick Connect dialog, if the port number was changed to something other than the default, the port number was reset to the default the next time the Quick Connect dialog was opened.
  • Windows: If a USB serial adapter was removed while the serial session was connected, SecureCRT could crash.
  • Windows: When the Windows 7 Areo snap feature was enabled, if the SecureCRT window was dragged so that it snapped to the side of the desktop and focus was switched to another application, when SecureCRT was restored from the taskbar, it reverted to its previous size.
  • Windows: If the Windows 7 Aero snap feature was enabled and SecureCRT was dragged by the title bar so that it was maximized using the snap feature, the SecureCRT window was partially off screen.
  • Mac: If the global option "Confirm when closing multiple tabs" was set and the "Do you wish to connect from all sessions?" prompt was displayed, SecureCRT closed even when "No" was selected.
  • Linux: On older processors, such as Pentium 4 or Pentium M, SecureCRT crashed when attempting to connect to a Secure Shell server.

New in SecureCRT 6.7.0 Build 172 (May 27, 2011)

  • SecureCRT 6.7 delivers a third major platform - Linux - with versions for Ubuntu and Red Hat. This release features a new Connect bar and many improvements to the button bar and scripting, like Python support in the script recorder and also copy and paste for button bar buttons.

New in SecureCRT 6.7.0 Build 137 Beta 3 (Apr 18, 2011)

  • Bug fixes:
  • If the Connect bar was removed from the toolbar through customization and then SecureCRT was restarted, attempting to bring up the customization dialog caused SecureCRT to crash.
  • If a script that called Crt.Screen.Send() was repeatedly run, it could cause terminal corruption and possibly a crash.
  • Under certain circumstances, after editing the Default session and attempting to apply the changes to all sessions, SecureCRT hung.
  • Scripts that called Crt.Screen.Send() to send end of line characters had different behavior than they did prior to version 6.7.
  • After pressing the ALT key and then the ENTER key, SecureCRT attempted to connect to a host named "".
  • When the SecureCRT window was resized by dragging the mouse, the rows and columns displayed in the status bar were not updated until the mouse button was released.
  • If the Connect bar was removed from the toolbar through customization and SecureCRT was restarted, the Global Options dialog incorrectly showed that the Connect bar was visible.
  • Mac and Linux: SecureCRT crashed when attempting to connect to a session with a misconfigured HTTP firewall.

New in SecureCRT 6.7.0 Build 123 Beta 2 (Mar 25, 2011)

  • Changes:
  • Removed warning message about toolbar and menu bar needing to be updated.
  • Linux: On Red Hat Enterprise Linux 5.5, the SecureCRT launcher icon is now installed into the Gnome system panel menu.
  • Bug fixes:
  • Windows: It was not possible to get the Connect bar back if it was removed from the toolbar.
  • Windows: The Connect bar did not work when it was placed on the menu bar.
  • Windows: On Windows 7, if the corner of the SecureCRT window was dragged to the top of the desktop, the full height option did not work.
  • Mac: When the accelerator COMMAND+` was used to cycle through the SecureCRT windows, a "`" character was inserted into the session.
  • Mac: If two sessions were connected in different windows and one of the sessions was maximized and the second session was dragged into the first window and then sent out to a new window, the second session was not the correct size.
  • Mac/Linux: If an invalid license was on the clipboard, the license wizard did not display the correct text.
  • Linux: On 32-bit Ubuntu 10.x, it was not possible to add SSH1 keys to the agent.
  • Linux: Selecting "Exit" from the File menu closed all SecureCRT windows instead of just the current window.

New in SecureCRT 6.7.0 Build 110 Beta 1 (Mar 9, 2011)

  • New features:
  • Linux versions for Ubuntu 10.x (32-bit and 64-bit) and Red Hat Enterprise Linux 5.5 (32-bit and 64-bit).
  • Added an optional connect bar, which allows a connection to be made by entering the host on the toolbar.
  • Added support for recording Python scripts.
  • Added the ability to add more than ten buttons to a button bar.
  • Added the ability to copy buttons from one button bar and paste them on another button bar.
  • Added the ability to move buttons within a button bar.
  • Added the ability to map a key or button to browse for a script to run.
  • Added the ability to configure the double-click tab action to be "Clone Tab in New Window".
  • Added an option to the Connect dialog to sort sessions logically, which is helpful when session names contain numbers.
  • In the Session Options dialog, added ability to sort columns in the Connection / Port Forwarding category.
  • Added support for in-line composition of IME characters so that IME characters are inserted into the session window as they are typed.
  • Added the script function FileOpenDialog() that displays the file browser and returns the selected file.
  • Added the script function ScriptFullName() that returns the full path and filename of the currently running script.
  • Added an optional parameter to the scripting function Connect() that allows pop-up messages to be suppressed.
  • Added the ability to specify a listening IP address when setting up a local or remote port forward from the command line.
  • Added a global INI-file-only option "Script MRU Count" that allows the number of scripts displayed in the recently used script list to be specified.
  • When the global INI-file-only option "Single Instance" is set and SecureCRT is already running, shortcuts that use the /S flag now open the specified session in a new tab.
  • Windows: Environment variables can be specified when assigning a "Run Script" or "Launch Application" function to a button or key.
  • Mac: If a file or folder is dragged to a local shell session, the path to the file is pasted into the session. When a file or folder is dragged to the remote session, there is now a "Paste Path" option on the menu that is displayed.
  • Mac: Added the ability to specify SecureCRT as the default Telnet handler so that HTML links to Telnet sessions connect to the specified session in SecureCRT.
  • Mac: Added support for the following character encodings: GB2312, BIG5 (950), Korean (949), Shift JIS (932).
  • Mac: Added support for the /T command-line option.
  • Changes:
  • Line and character send delay settings are now honored for buttons and keys mapped to send strings.
  • When pasting text into SecureCRT, LF is converted to CRLF.
  • The session option "Enforce X11 Authentication" can now be set in the Session Options dialog. Previously, it had to be set manually in the session .INI file.
  • The button and keymap Menu function MENU_TAB_NEXT now has the same behavior as pressing and releasing CTRL+TAB. The Menu function MENU_TAB_PREV now has the same behavior as pressing and releasing SHIFT+CTRL+TAB.
  • If a script is already running and an attempt is made to run another script, a message is displayed.
  • Windows: Entering the license data now registers the application for all users instead of only for the current user.
  • Mac: Scrolling performance has been improved.
  • Mac: The auto session list now displays icons for the items in the list.
  • Mac: The history, readme, and EULA files are installed in the /Library/Application Support/VanDyke/SecureCRT folder.
  • Bug fixes:
  • If SecureCRT closed while a dialog was being displayed, it crashed.
  • If an escape sequence that sent a large file (1 MB or larger) was running and SecureCRT was exited during the send, it crashed.
  • If a script set a session's columns to be larger than the maximum number of columns and then that session was used, SecureCRT crashed.
  • SecureCRT could crash if it was in the process of closing and a script attempted to access an object that no longer existed.
  • SecureCRT could crash when a second instance was started.
  • SecureCRT terminal locked up after exiting a remote command such as "vi" or "man" if the window was resized while the command was running.
  • Python scripts that contained a Unicode character in the script name could not be run.
  • In some cases, screen reading software such as JAWS was not able to track the cursor when the cursor style was set to "Block". If the "Use trackable insertion carat" option is set, the "Vertical Bar" cursor style is now used.
  • If a key or button was mapped to launch an application that did not have an ".EXE" file extension and an argument was specified, the specified argument was not saved.
  • If a session used ANSI color and a color scheme and the scrollback buffer contained text, if ANSI color was disabled and re-enabled, some characters in the scrollback buffer were displayed using incorrect foreground and background colors.
  • Highlighted text sometimes flickered.
  • In the Connect dialog, if the right mouse button was clicked on title bar or toolbar, the context menu was not displayed at the mouse cursor.
  • Telnet: When an unrecognized IAC SB option was received, garbage was displayed in the session.
  • SSH1/SSH2: On Windows Vista and Windows 7, if "localhost" was specified for port forwarding, it resolved to an IPv6 address, which caused the port forward to fail.
  • SFTP: In the SFTP tab, when an "ls" command was issued and the files had long names, the spacing of the output was not correct.
  • SFTP: In the SFTP tab, tab completion did not work with character encodings such as utf-8, koi8-r, and OEM=cp866.
  • Windows: When a Perl script was specified on the SecureCRT command line, an error was thrown if the script called Crt->Quit().
  • Mac: SecureCRT crashed if a session was being renamed from the Connect dialog and then another action such as Edit or Delete was performed on that session.
  • Mac: Viewing a host key could cause SecureCRT to crash.
  • Mac: On keyboards where "+", "]", and "*" are on the same key, keyboard shortcuts using those keys did not work in applications such as vi and vim.
  • Mac: If a script was launched from a button or mapped key, the script could not be cancelled from the Script menu.
  • Mac: If SecureCRT was displayed on a second monitor that was larger than the first monitor and was later run with only the first monitor connected, it was not possible to resize the window to fit on the screen.
  • Mac: If the SecureCRT window was moved to a different location before connecting to a session and then it was exited, flashing occurred the next time SecureCRT started.
  • Mac: If "%U" was specified in the Title bar for a local shell session, the user name was not substituted.

New in SecureCRT 6.6.2 Build 350 (Feb 3, 2011)

  • Introduces the first version for Mac OS X systems, with a full complement of advanced session management, security, terminal emulation and automation capabilities.
  • Windows and Mac versions alike feature cross-platform scripting with Python and a "Send Binary" file transfer option.