VanDyke Software

SecureCRT History

           SecureCRT(R) 9.0.1 (Official) -- March 18, 2021

            Copyright (C) 1995-2021 VanDyke Software, Inc.
                        All rights reserved.

This file contains the SecureCRT product history.  It includes lists 
of new features, changes, and bug fixes sorted by release.  For a 
product description, installation notes, registration information,
and contact information, please refer to SecureCRT_README.txt
(downloaded with this installation).

Changes in SecureCRT 9.0.1 (Official) -- March 18, 2021


  - 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

  - 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

  - Mac/Linux: Under certain scenarios, opening a tab in a new tab
    group caused the terminal view to be blank.

Changes in SecureCRT 9.0 (Official) -- February 18, 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.

Changes in SecureCRT 9.0 (Beta 6) -- February 9, 2021


  - The default file type for the scratchpad File Open dialog is
    "All Files".

Bug Fixes:

  - When moving focus to the SecureCRT terminal view using a mouse
    click, if tmux was running in the connected session, tmux's
    "copy mode" may have been unexpectedly activated.

  - When attempting to run a Python 3 script that had a UTF-8 byte
    order mark (BOM) specified in the file, the script failed to run.

  - If a send string button or command had a label that ended with
    three single quote characters, when SecureCRT restarted, the label
    text was appended to the Send String text and the label was now

  - Windows: When a Command Manager send string command that contained
    three sequential single quote characters was copied to the Button
    Bar, SecureCRT could crash.

  - Windows: When connecting to an RDP host, if the Microsoft RDP
    client had previously saved credentials for the same host, those
    saved credentials may have been used, even when the user specified
    within SecureCRT was different.

  - Windows: Under certain scenarios, opening a tab in a new tab group
    caused the terminal view to be blank.

  - Windows: When the main window was resized while a session was
    connected, the rows and columns became out of sync between the
    remote and SecureCRT.

  - Windows: When saving a new Scratchpad file, the file encoding was
    set to "UTF-16 LE,"  which could have prevented Python script files
    created using the scratchpad from being run by SecureCRT.

  - Mac: When importing a configuration that included Command Manager
    commands, the commands did not appear in the Command Manager until
    after restarting SecureCRT.

  - Mac/Linux: If the SSH agent was not running or was in a bad state
    on the local system, connecting to a session with a valid public
    key may have failed even though the agent was not required.

Changes in SecureCRT 9.0 (Beta 5) -- January 26, 2021


  - Windows: When using a PKCS#11 provider DLL that did not match
    the architecture (32 vs. 64 bit) of the client, a misleading
    error was displayed.  The error message has been modified to
    describe the error more accurately.

Bug Fixes:

  - When an 80/132 column switching sequence was received in a
    secondary tab, the window and terminal size may not have
    adjusted as expected.

  - Windows: If different versions of SecureCRT and SecureFX were
    installed into the same location, either application could have
    crashed when making a connection.

  - Windows: When SecureCRT and SecureFX were installed as a
    combined installation (integrated), opening a session that had
    a terminal-only protocol set (e.g., RDP, Serial, TAPI, Local
    Shell) could have resulted in a crash.

  - Windows: When SHIFT+Insert was used to paste text into the
    Session or Command Manager filter field, the text was pasted
    to the active session instead.

  - Windows: When a Scratchpad tab was opened and a block of text
    was selected using ALT+, entering replacement text via
    the keyboard only replaced the last selected line.

  - Windows: When viewing the Session Options dialog, certain
    display configurations resulted in scroll bars appearing in
    the category tree.

  - Windows: Under certain scenarios, the SecureCRT taskbar icon
    could shift to the right most position on the taskbar when
    connecting to a session.

  - Windows: Under rare circumstances, when connecting to an RDP
    session, if the window had to resize to account for the session
    size, a reconnect prompt may have been displayed after the
    window resized.

  - Mac: If the default font could not be loaded when SecureCRT
    started, a crash could occur.

  - Mac: If Python 3 was installed via Homebrew, SecureCRT may not
    have been able to find the Python scripting engine.

  - Mac: When opening a Telnet URL or launching SecureCRT with the
    /T command-line option, if SecureCRT was already opened, the
    connection was unexpectedly opened in a new instance of

  - Mac: Dragging a session or folder into another folder caused
    that session or folder to be hidden from view.  A restart of
    the application caused the folder or moved session to be
    displayed correctly.

  - Mac: When using "Update Now..." to check for and download an
    updated installer, the progress dialog was not shown for the
    initial check or during the download.

  - Linux: When the application ran over X11 forwarding and the
    window size became too large, a crash could occur.

  - Linux: Using a keyboard shortcut to enter a combining character
    (e.g., รณ) may have failed.

  - Linux (RHEL 8): When attempting to install SecureCRT and
    SecureFX in parallel using standalone installers (i.e., not
    the scrt-sfx combined installer), the installation of the
    second application would have failed due to unexpected file

  - Linux (RHEL 7/8): When SecureCRT was uninstalled, the
    "/usr/local/lib/SecureCRT" folder was not removed.

Changes in SecureCRT 9.0 (Beta 4) -- December 15, 2020


  - Windows: Added /RDP protocol command-line option for opening
    an ad hoc RDP connection.

  - Windows: Disconnected RDP tabs/tiles are now reused if the
    "Reuse disconnected tabs" global option is set.

  - Windows: When an RDP session is moved to a new or different
    SecureCRT window, a prompt is no longer displayed.

Bug Fixes:

  - When the option "Display Logon prompts in terminal window" was
    set, logging into an OpenSSH server failed if the password
    contained a Unicode character.

  - If the remote system sent an unterminated title escape sequence
    followed by the start of a new title escape sequence, the title
    data was displayed in the view.

  - Windows: Under certain scenarios, the number of columns set for
    a connected session could have exceeded the maximum number of
    columns allowed, resulting in a crash.

  - Windows: When authenticating with a certificate that was accessed
    via CAPI or a PKCS #11 provider, authentication to certain servers
    could have failed.

  - Windows: When connecting to multiple RDP sessions simultaneously,
    not all sessions would have been opened.

  - Windows: If the SecureCRT window was positioned on the display
    using the Windows Aero Snap feature, zooming the text caused
    the main window to change size.

  - Windows: A scratchpad or script editor file could not be opened
    a second time.

  - Mac/Linux: If a Python script referenced a SessionConfig object,
    SecureCRT may have crashed.

  - Mac: If a local shell session was closed while "sz" or "lsz" was
    sending data, SecureCRT could have crashed.

  - Mac: When all the sessions were being edited, if the color scheme
    was changed and then the Session Options dialog was dismissed,
    SecureCRT could have crashed.

  - Mac: When using the Apple Braille or Apple Clor Emoji fonts,
    text was not displayed as expected in the terminal view.  These
    fonts are no longer available for selection.

  - Linux: When running SecureCRT over X11 forwarding and the X11
    server was either misconfigured or not running, the application
    would crash at startup.

Changes in SecureCRT 9.0 (Beta 3) -- November 19, 2020

New Features:

  - Windows: Added the ability to open files into a scratchpad tab
    or tile.

  - Mac: Added support for a Command Manager, which allows commands
    to be saved and organized within folders.  Commands that can be
    saved include: sending strings, executing menu functions, running
    scripts, and running local applications.  Also, button bars,
    including the buttons on the button bar, can be copied to the
    Command Manager and vice versa.

  - Mac: Added support for Python 3.  An external Python 3.8 engine is

  - Linux: Added support for Ubuntu 20.04.

  - Linux: Added support for Python 3.  On Ubuntu 20.04, the default
    Python 3.8 version is supported.  On Ubuntu 18.04 and RHEL 8, the
    default Python 3.6 version is supported.


  - The prompt for keys that are pre-loaded into agent now shows the
    filename associated with the key.

  - SSH2: When attempting an SSH2 connection, if KEX algorithm
    negotiation fails, SecureCRT offers to try again by enabling
    a supported algorithm.

  - The SHA-2 base64 hash of the public-key fingerprint is now
    displayed in the Public Key Properties and trace output.

  - Windows: RDP sessions now support smart cards.

  - Windows: RDP sessions no longer have to reconnect when the
    application window is resized.

  - Windows: The RDP option "Scaling" was changed to "Smart sizing"
    and a new "Scale factor" option was added.

  - Windows: Added the ability to disconnect and reconnect RDP

  - Windows: RDP sessions honor the global options "Exit when last
    session is disconnected" and "Show connection closed dialog".

  - Windows: If there are unsaved changes in a scratchpad tab or
    tile, when the tab or tile is closed, a prompt asking if the
    changes should be saved is displayed.

  - Mac: For new installations, the Kerberos key-exchange methods
    are off by default.

Bug Fixes:

  - If a very large file was specified as a public-key file,
    SecureCRT could crash when the file was loaded.

  - When attempting to connect to a server that did not reply to
    SSH_MSG_CHANNEL_REQUEST, SecureCRT could hang.

  - When connecting to a session that used public-key authentication,
    if the specified key did not exist on the remote system, the
    file browse dialog displayed to allow another public-key file to
    be selected had "::rawkey" text included in the file name field.

  - When using newer versions of Vim, a "2m" character sequence may
    have appeared on the screen due to an unsupported XTMODKEYS
    escape sequence.

  - Windows: When connecting to an RDP session, the scaling settings
    set on the local display were not honored.

  - Windows: If the "Reuse disconnected tab" global option was set
    and an RDP session was disconnected, attempting to connect
    another session silently failed.

  - Windows: When the session options were changed for a
    disconnected RDP session, the changes were not honored when the
    session was reconnected.

  - Windows: When connecting to an RDP session with the "Fit to
    panel" and "Scaling" display options enabled, if the window
    mode was set to tiled, the RDP view did not correctly scale to
    fit the window.

  - Windows: When an RDP session was connected and had focus,
    using ALT+TAB to switch to a different window, then back to
    SecureCRT did not put focus back into the RDP session.

  - Windows: If the "Show confirm disconnect dialog" option was
    enabled, disconnecting an RDP session did not prompt with the
    confirmation dialog.

  - Windows: When SecureCRT and SecureFX were installed as a
    combined installation (integrated) and an RDP session was
    created using the Quick Connect dialog, the transfer protocol
    was unexpectedly set to SFTP.

  - Windows: The scratchpad tab or tile was closed when "Close
    all not connected" was selected.

  - Windows: When pasting long lines of text into a Scratchpad
    session, the horizontal scrollbar may not have been displayed.

  - Windows: When a scratchpad session was opened in a maximized
    window in cascade mode, the scrollbars were not shown and
    hidden as expected.

  - Windows: When saving the scratchpad contents to a file using
    "Save As", the document filter type may have been unexpectedly
    set to Script.

  - Windows: If a scratchpad's name was changed and "Save As" was
    selected in the context menu, the name in the "Save As" dialog
    had an extra space at the end.

  - Windows: If scripting was administratively disabled, the Script
    menu was displayed the first time SecureCRT started.  Note that
    any attempts to run a script still failed as expected.

  - Windows: When zooming in to increase the font size in the
    current terminal view, the font size may not have been the
    correct size after zooming back out the same number of times.

  - Windows: When the main window was maximized after closing the
    first opened tab, the terminal view of the remaining tabs was
    the incorrect size, causing the right side of the view to no
    longer scroll text and causing the lower portion of the view
    to appear blank.

  - Mac: When the number of available columns was less than the
    actual terminal view space and the application window was
    maximized, attempting to open another tabbed session or entering
    enough text in the second tabbed session to cause it to expand
    past the maximum number of columns could have resulted in a crash.

  - Mac/Linux: When the close tab keyboard shortcut (Command+W or
    Ctrl+F4) was sent to all tabs via the Command Window, SecureCRT
    could crash.

  - Mac: Attempting to authenticate using a YubiKey smart card with
    the "" library specified as the PKCS#11 provider
    resulted in an error, because the library could not be loaded.

  - Mac: The application window was sometimes blank after regaining
    focus from another application, such as f.lux.

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

  - Mac: When using the built-in trackpad on a MacBook to drag a
    session to a different location in the Session Manager, auto-
    scroll and folder auto-expand did not work consistently.

  - Mac: After setting the font typeface for a session in the Session
    Options dialog, it was not possible to select a different font

  - Mac: When using certain fonts (e.g., Source Code Pro), not
    all of the font's typefaces could be selected.

  - Mac: Under certain circumstances, when an auto-hidden Session
    Manager was expanded, the Session Manager would briefly open,
    then immediately re-hide.

  - Mac: If the Session Manager was docked and in auto-hide mode, a
    "<>" text artifact appeared on the Session Manager tab when

  - Mac: If SecureCRT was open and the system appearance setting was
    changed from Dark Mode to Light Mode, the labels on the Button Bar
    buttons were too light.

  - Mac/Linux: If the Command Window "Send Characters Immediately"
    option was enabled, minimizing and restoring SecureCRT caused the
    option to be disabled.

  - Mac/Linux: When the close tab keyboard shortcut (Command+W or
    Ctrl+F4) was sent to all tabs via the Command Window, SecureCRT
    could crash.

  - Mac/Linux: When a public key that had a comment specified in the
    key data was added to the agent, the Manage Agent Keys dialog did
    not display the comment.

  - Mac/Linux: When enabling logging via the file menu, connecting to a
    session caused logging to be toggled off.

  - Mac/Linux: Text displayed on the Keyboard Interactive and View Host
    Key dialogs could not be selected or copied.

  - Linux: On systems with a display scaling factor set greater than
    100%, the menu text and toolbar icons may not have scaled correctly.

Changes in SecureCRT 9.0 (Beta 2) -- October 20, 2020


  - On the right-click terminal menu, changed "Google Selection" to
    "Lookup Selection".  The search engine to use for the lookup can
    be specified in a global INI-file-only option.

  - Each tabbed session now has its own font, character encoding,
    and zoom level.  Note: This change was inadvertently omitted
    from the Beta 1 release notes.

  - A local shell session can be specified on the command line and
    in a script by using the /LOCALSHELL command-line parameter.

  - Windows: Added the ability to rename a scratchpad tab or tile.

  - Windows: When more than one scratchpad is opened, a number "(n)"
    is appended to the "scratchpad" tab/tile name.

Bug Fixes:

  - When exporting the configuration to a file, if a folder name was
    specified instead of a filename, the export file was created using
    the folder name and the folder itself was renamed with a ".bak"

  - Dragging a terminal session tab to another SecureCRT window failed
    if a scratchpad tab had focus in the other window.

  - When the Xterm "True Color" color mode was enabled, colors were
    not displayed correctly for certain remote applications (e.g.,

  - The Command window height was not retained if the Command window
    titlebar was disabled.

  - When starting SecureCRT from the command line, if the /I option
    was used to specify the public-key file to use for authentication,
    it was ignored.

  - When tab completing an SFTP tab path that contained a backslash
    character, the path components preceding the backslash were

  - Windows: When JAWS screen reader was running, SecureCRT failed
    to start.

  - Windows: SecureCRT was not able to load the Anaconda Python 3.8
    script engine.

  - Windows: When multiple tabs had been opened and the first tab was
    then closed, the window could no longer be resized.

  - Windows: On high DPI monitors with certain scaling factors set,
    the toolbar icons and certain dialog text appeared blurry.

  - Windows: On systems with a large display scaling factor set
    (i.e., 300% or greater), the toolbar icons were not displayed

  - Windows: When using the "New Session Wizard" to create an RDP
    session, if the domain was specified as part of the username
    (i.e., domain\username), the resulting session duplicated the
    domain (i.e., domain\domain\username).

  - Windows: When an RDP session was connected to xrdp with "Fit to
    panel" and "Scaling" options enabled, the reconnect operation
    that happens when the window is resized failed.

  - Windows: When RDP was specified as the terminal protocol for the
    Default session, the RDP options were grayed out and could not be

  - Windows: When a scratchpad or script editor tab was active, the 
    application titlebar was not updated.

  - Windows: After saving the contents of a scratchpad tab or tile
    to a file, the file could not be opened in another application.

  - Windows: In the "Save As" dialog for the scratchpad, the default
    filename "scratchpad.txt " contained an extra space.

  - Windows: Connecting to a session while the main window was
    maximized and the session window was set to open in cascaded
    tile mode could have resulted in a blank session window being

  - Windows: If the default.mnu file was specified as a custom .MNU
    file, pressing CTRL+INSERT caused the terminal view to zoom in
    instead of copying the selected text.

  - Windows: Under rare circumstances, text in the scrollback was
    only visible when selected.

Changes in SecureCRT 9.0 (Beta 1) -- September 24, 2020

New Features:

  - Windows: Added support for RDP.

  - Windows: Added support for Python 3.  Python 3.8 (available
    at must be installed and the script's first line
    must be: # $language = "python3".  Since support for Python 3
    is provided through an external module, Python 3 libraries
    can be used in SecureCRT scripts.

  - Windows: Added a scratchpad, which has basic editing
    capabilities, allowing notes to be taken in a tab (or tile).

  - Windows: Added a script editor with syntax highlighting, which
    allows local scripts to be edited in a tab (or tile).

  - Added the ability to specify public/private keys to load into
    SSH2 agent when SecureCRT starts.

  - The status bar has been enhanced so that items can be rearranged
    and items that aren't being shown do not take up space on the
    status bar.

  - Added the ability to show the local system time in the status

  - When a selection is being made, the number of lines currently
    selected is shown in the status bar.  Because only whole lines
    are counted, the selection must start at the beginning or end
    of a line.

  - Added a global option that allows the status bar to be shown
    in full-screen mode.

  - Added support for the rsa-sha2-256 and rsa-sha2-512 public-key
    algorithms (RFC 8332).

  - Added the ability to do a Google search on text selected in a

  - Added the ability to use wildcard characters "*" and "?" in the
    Session Manager filter box.

  - The multi-line paste option now allows the number of lines to
    be specified, providing additional control over when the Paste
    Confirmation dialog is shown.

  - Added an option that allows the Xterm escape sequence to copy to
    the clipboard (OSC 52).

  - SSH2: The host-key algorithms can now be specified and ordered
    in the Session Options dialog.

  - Windows: Added an administrative option that disallows a blank
    configuration passphrase.


  - SSH2: Removed support for several weak ciphers (Blowfish and RC4)
    and MACs (SHA1-96, MD5, and MD5-96).

  - In the multi-line paste confirmation dialog, the line-send delay
    value can be specified for the paste operation.

  - For TN3270 emulation, the default mapping of the Enter key was

  - Added the ability to reorder sessions in the Auto Session list.

  - When connecting to a ProFTPD mod_sftp server, SFTP version 3
    is used by default.

  - When IPv6 hostnames are displayed in tabs or the application
    title bar, the colons (":") are no longer replaced with
    underscores ("_").

  - In the Manage Agent Keys dialog, the fingerprint is displayed
    as SHA-2.

  - For new keyword lists, the default Highlight style is "Color"
    instead of "Reverse video".

  - Added a session INI-file-only option "Alternate Screen Output
    Added To Scrollback" which allows alternate screen (e.g., tmux)
    output to be put in the scrollback buffer.

  - In the Global Options dialog, in the SSH Host Keys category,
    the Hostname and Port columns now sort logically instead of

Bug Fixes:

  - If the "Display logon prompts in terminal window" option was
    enabled and the remote password contained a Unicode character,
    authentication may have failed to certain servers.

  - When attempting to connect to an ownCloud WebDav server, the
    initial connection and/or traversing the file system could have

  - When connected to a remote host using the Raw protocol, data
    displayed on the screen could have been corrupted.

  - When connected to a Telnet server that did not respond to Kermit
    binary mode transition requests correctly, the Kermit transfer may
    have failed.

  - The display of certain Unicode characters (e.g., emojis) in
    the terminal could have caused other characters to appear as

  - Some global options did not take effect immediately after being
    set and saved in a script.

  - When using a mapped key configured to launch an application with
    an argument, the application failed to launch.

  - When using tab completion within an SFTP tab, filenames that
    contain spaces may not have autocompleted as expected.

  - When connected to certain remote systems and running applications
    (e.g., Aptitude) that support menu interaction using the mouse,
    clicking on a top level menu item may not have correctly displayed
    the dropdown menu.

  - When a log file was created in a location that contained a "."
    character somewhere in the path, the ".log" extension was not
    automatically appended to the filename.

  - If a session's log file path included the %F session folder
    replacement parameter and the "Start new log at midnight"
    logging option was enabled, the log file path used on the new
    day excluded the %F folder.

  - When the same session was connected multiple times
    simultaneously, the Session.LogFileName script function did
    not return the correct log filename for any of the secondary

  - When editing multiple sessions simultaneously, and the state of
    the Logon Action "Hide" option was changed, only the first session
    was updated with the new value.

  - When the ImportArbitraryData example script was used to create
    thousands of sessions, and the session database already contained
    thousands of sessions, the session creation became very slow.

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

  - With certain network configurations, the TFTP server's listen
    address was incorrectly displayed on the status bar as a
    169.254.*.* IP address, which is reserved for Automatic Private
    IP Addressing (APIPA).

  - Windows: If the internet connection was disconnected while
    downloading an available update via "Update Now...", the
    VanDykeUpdate application could have crashed.

  - Windows: When using CAPI to access a certificate located on a
    smart card, if the CAPI store contained multiple certificates,
    there could have be a delay before being prompted for the smart
    card pin.

  - Windows: If the Session Manager and Command Manager were
    docked in stacked layout, the size of the individual manager
    windows was not retained between instances of SecureCRT.

  - Windows: When the Command Window was displayed, the height of
    the window increased by one pixel each time SecureCRT was

  - Windows: If the Session Manager and Command Manager were docked
    within the same pane and configured to be auto-hidden, the
    expanded size of the managers could change when SecureCRT was

  - Windows: After upgrading from SecureCRT 6.5 or earlier,
    previously mapped keys that were configured to launch an
    application with arguments may have failed to work.

  - Windows: On high DPI monitors with a large scaling factor set,
    text displayed on the Keyboard Interactive authentication prompt
    could have been cut off.

  - Windows: When opening the "Script->Run..." dialog, the script
    name that was pre-populated in the filename field was partially
    scrolled out of view.