
             SecureCRT(R) 9.6.3 (Official) -- May 8, 2025

            Copyright (C) 1995-2025 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.6.3 (Official) -- May 8, 2025
----------------------------------------------------

New Feature:

  - Windows: SecureCRT officially supports Windows Server 2025.

Bug Fixes:

  - If a session had a disabled dynamic port forward entry,
    connection attempts using that session as a firewall failed.

  - In a TN3270 session, pasting data too long for a field resulted
    in data overflowing into adjacent fields.

  - Keyboard input could freeze in TN3270 sessions after toggling
    insert mode.

  - Data sent over serial connections had a noticeable delay
    displaying in the session view.

  - The Command Window reverted to sending commands to the active
    session when all session tabs were closed, regardless of the
    "Send Commands to" setting.

  - Terminal sessions incorrectly displayed the character 'p' in
    place of DECRQM escape sequences.

  - Converting a VanDyke-format SSH keypair to OpenSSH format used
    the old OpenSSH format instead of the new format.

  - The "- SecureCRT" suffix was always appended to the 
    application window title bar, even when the title bar was
    set with a global option, script, or /TITLEBAR command-line
    argument.

  - If a session logged a custom "Upon disconnect" message and the
    session was closed without first disconnecting, the disconnect
    message was logged twice.

  - Windows: SecureCRT could crash due to a third-party dependency
    when using AES-GCM algorithms.

  - Windows: If a scratchpad tab was part of a group of sessions
    being sent to a new window, SecureCRT crashed.

  - Windows: SecureCRT could crash if multiple top level windows
    were closed at the same time.

  - Windows: When going into full-screen mode from a maximized
    window, SecureCRT may have appeared behind the Windows taskbar.

  - Windows: Certain USB-Serial adapters or virtual COM port
    emulators did not appear in the Port dropdown list when
    creating a Serial session.

  - Mac/Linux: When using a configuration copied from Windows that
    included a scratchpad auto session, SecureCRT crashed at
    startup.

  - Linux: SecureCRT could hang on launch if checking for available
    application update failed.


Changes in SecureCRT 9.6.2 (Official) -- February 20, 2025
----------------------------------------------------------

Bug Fixes:

  - Options for a currently open session that were changed from the
    Session Manager were not saved or applied.

  - Importing credentials that were exported from a configuration
    using a personal data folder into a configuration using a single
    folder could have resulted in empty credential entries.

  - Some global and session options were not saved when imported from
    an XML file. 

  - Invalid global and session option integer values could have been
    imported from an XML file.

  - The cursor blinked while typing in a session.

  - Reverse video artifacts could have appeared in the terminal
    window when displaying dense output.

  - Sessions using VT320 emulation incorrectly reported VT220 device
    attributes.

  - Windows: Upgrading SecureCRT via a silent install with an answer
    file could have failed to upgrade protocol DLLs, causing the
    upgraded version to fail to start.

  - Windows: The scrollback buffer in localshell sessions could
    have been truncated when the window was resized.

  - Windows: When connecting to a SecureCRT terminal session from
    SecureFX, the SecureCRT window may not have received focus as
    expected.

  - Windows: Moxa COM ports were not included in the port dropdown
    list when creating a Serial session.

  - Windows: When using one of the legacy display themes, an
    unexpected lag may have been present when scrolling through
    sessions in the Session Manager.

  - Mac/Linux: Adjusting the font size while SecureCRT was snapped,
    pinned, or docked to one position on the screen could have caused
    the application window to resize.

  - Linux: SecureCRT could have crashed if a dialog was opened as a
    session was closing.


Changes in SecureCRT 9.6.1 (Official) -- December 17, 2024
----------------------------------------------------------

Bug Fixes:

  - SecureCRT crashed if a script launched and closed a session that
    used a logon script.

  - When authenticating with an OpenSSH Trusted Certificate, if the
    .pub file was specified as the public key, authentication failed.

  - Global SSH2 settings were not updated after being imported from an
    XML file.

  - Under certain circumstances, some global and session options were
    not updated after being imported from an XML file.

  - Windows: When importing a configuration that changed the protocol
    for an existing session, the icon displayed in the Session
    Manager indicating the session protocol was not updated.

  - Windows: The status text for scratchpad editors did not update in
    tiled mode.

  - Mac/Linux: The session name and status were truncated with elipses
    when switching from tabbed to tiled mode.


Changes in SecureCRT 9.6 (Official) -- November 19, 2024
--------------------------------------------------------

No changes.


Changes in SecureCRT 9.6 (Beta 5) -- November 12, 2024
------------------------------------------------------

Bug Fixes:

  - When a public key was specified in a session's public key
    properties, SecureCRT did not check the agent for the matching
    private key before trying all available keys.

  - When connecting through a SOCKS proxy, if the SOCKS packet data
    was spread over multiple TCP packets, the connection could have
    failed.

  - When importing FTPS or HTTPS sessions, the FTPS/HTTPS-specific
    session options were not imported correctly.

  - When firewall configurations were included in an XML file
    import, existing firewalls with the same name were not updated
    with the new settings.

  - Windows: The Active Sessions Manager displayed the wrong status
    indicator icon for a session if it failed to connect and was
    the only open session.

  - Windows: When using a legacy theme (e.g., Shaded), certain
    toolbar buttons may have used the incorrect icons.

  - Mac: When a local shell session was disconnected, SecureCRT
    could have crashed.

  - Mac: If the configuration was inaccessible, SecureCRT would
    silently exit instead of displaying an error message.


Changes in SecureCRT 9.6 (Beta 4) -- October 24, 2024
-----------------------------------------------------

Change:

  - Mac/Linux: Proxy commands specified in firewalls will use the
    user's shell environment.

Bug Fixes:

  - When the "Close on disconnect" and/or "Mapped Keys" settings
    were changed for the default Local Shell session, new Local
    Shell sessions did not honor those changes.

  - Windows: When the RDP Scale Factor option was changed from
    "Match desktop" to a specific scale factor, the change was not
    saved.

  - Windows: When using cascaded window mode, clicking into the view
    of an RDP session did not move that session window to the
    foreground.

  - Windows: When right-clicking a session in the session manager,
    the "Find" menu icon may have displayed incorrectly if multiple
    SecureCRT windows were open.

  - Windows: Custom menus based on 'default.mnu' did not include
    the "RDP Defaults" option.


Changes in SecureCRT 9.6 (Beta 3) -- October 1, 2024
----------------------------------------------------

Change:

  - When using a personal data folder, if the configuration path is
    changed in the Global Options dialog, the personal data folder
    will be updated to match only if it has the same path.

Bug Fixes:

  - A session with an "Inactive" connection status did not change to
    "Connected" when the session was viewed or selected.

  - When connected to a session using TN3270 emulation, the function
    keys may not have sent the expected data.

  - Windows: SecureCRT did not report the "connection was denied
    because the user account is not authorized for remote login"
    error when connecting to a system where RDP access was denied
    for the specified user.

  - Mac: When using a PKCS #11 library to access certificates on a
    smart card, the Select Certificate dialog did not display the
    certificates on the smart card.

  - Mac: PKCS #11 provider libraries with a .so extension were not
    selectable from the Public Key Properties dialog.

  - Linux: Using the Terminus font in a session and zooming to adjust
    the font size could have resulted in a crash on Ubuntu 22.

  - Linux: The application window had a pitch-black background on
    Ubuntu 22 when in dark mode.


Changes in SecureCRT 9.6 (Beta 2) -- August 28, 2024
----------------------------------------------------

Bug Fixes:

  - SecureCRT did not properly wrap tab-delimited text.

  - When selecting a certificate using PKCS #11 in the Public Key
    Properties dialog, the "Get username from certificate" option
    was unselectable.

  - Windows: Reconnecting to a disconnected RDP session tab could
    have caused SecureCRT to crash.

  - Windows: When multiple SecureCRT windows were open, switching
    the display theme may have caused the SecureCRT window to paint
    incorrectly.


Changes in SecureCRT 9.6 (Beta 1) -- August 15, 2024
----------------------------------------------------

New Features:

  - Specific folders and sessions can be selected and exported to an
    XML file.

  - Added the ability to include the sensitive configuration data
    contained in the personal data folder when doing an XML export.

  - Added the ability to prevent sensitive data such as passwords
    and usernames from being included in an XML export.

  - Added the ability to change the hostname (or IP address) for
    multiple sessions at the same time.

  - Added the ability to map a button, key, or command to send a
    string to the Command window.

  - Added the ability to map a button, key, or command to select the
    next or previous button bar.

  - Added the ability to set the cursor style to blinking line or
    steady line via an Xterm escape sequence.

  - Added a session option to ignore the clear scrollback escape
    sequence (\033[3J). 

  - Added a "%C" substitution parameter, which can be mapped to a
    folder on Windows, macOS, or Linux, and used in the X/Y/Zmodem 
    upload or download directories or in the log file path.

  - Added the ability to accept OpenSSH trusted certificates as host
    keys.

  - Added support for SSH private keys encrypted with the AES-256-CBC
    cipher.

  - Windows: Added two new administrative options ("Disable Automate
    Logon Expect/Send" and "Disable Automate Logon Script"), which
    provide more granular control of automated logon actions than the
    administrative option "Disable Automate Logon". 

  - Windows/Mac: Added support for Python version 3.12 and 3.13.

  - Mac/Linux: Added a new Firewall type "Proxy command" which
    allows a local proxy command to be run when connecting to a
    remote server.

  - Linux: Added support for Ubuntu 24.04 LTS.

  - Linux: Added support for Python 3.12 scripts.

  - Linux: The system appearance Light or Dark setting is honored by
    the SecureCRT application window.

  - Linux: Added the ability to zoom sessions using the keyboard
    and the scroll wheel.

Changes:

  - Support for the Python 3.8 scripting engine has been removed.
    SecureCRT supports newer versions of the Python scripting engine
    as listed in the "System Requirements" topic of SecureCRT's
    built-in help.

  - The Hostname can now be modified when editing multiple sessions.

  - The Manage Agent Keys dialog now supports multi-selection and
    bulk removal of keys.

  - For new configurations, the default value for the Global.ini file
    option "Max Scrollback Buffer Size" has been changed from 128,000
    to 1,024,000, which allows Session Options to be configured with a
    scrollback buffer size of up to 1,024,000 lines by default.

  - The inactive window transparency lower limit has been changed
    to 1.

  - When a session is waiting for the string specified by the prompt
    delay option, the status bar now displays a message to indicate
    that the session is waiting.

  - Session and editor tabs in the Active Sessions Manager can
    be closed via the context menu or with the Delete key.

  - The session status is displayed as text in the titlebar for
    tiled sessions.

  - In the Session Options dialog, the local shell pre-connect
    command option is grayed out when it is not valid for the
    terminal protocol.

  - For XML exports of sessions, button bars, commands, and host keys
    no longer have to be included.

  - For XML exports, the hostkey database is only included by
    default when "Global Options" is selected.

  - Public-key information is now stored in the personal data folder
    if it is being used.

  - The session logon script and its associated settings are now
    included in the personal data store when it is being used.

  - When enabling a personal data store, the personal data folder
    path must now be an empty directory.

  - When using a personal data store, the personal data folder path
    will update to match any changes made to the public configuration
    folder.

  - SecureCRT no longer puts quotes around the comment when
    generating keys.

  - Trace output no longer shows window-change events for session
    font changes.

  - vsh/vsftp/vcp: Added a command-line option "--license-info" that
    outputs the license data.

  - VRALib (Windows): For a Connection object, "http" can be specified
    as the FirewallType.

  - VRALib (Windows): Added the properties "IsRegistered" and
    "LicenseData" to the License Object.

  - Windows: The installer is now compliant with Microsoft guidelines
    for Single Package Authoring (dual-purpose package), which allows
    per-machine and per-user installations.

  - Windows: Tab tooltips now include the session's connection
    status.

  - Windows: When no sessions are connected or the active tab is an
    RDP session or scratchpad, the status bar no longer displays
    Rows and Cols information.

  - Windows: When adding a new credential, the Public Key Properties
    dialog can now be opened before a credential title and username
    have been specified.

  - Windows: For RDP sessions, when the remote system is rebooted,
    the message box informing the user that the session is ending
    and restarting is no longer displayed.

  - Mac: Improved scrolling performance when a Local Shell session
    outputs data.

  - Mac: Changes to the system's cursor blink rate are now reflected
    in SecureCRT sessions.

  - Mac: Title bars, toolbars, and status bars no longer have a
    gradient style.

  - Mac/Linux: When the mouse hovers over a tabbed session, a tootip
    containing the tab title and connected status is displayed.

Bugs Fixes:

  - When multiple sessions were connecting through the same dependent
    session firewall, SecureCRT could have crashed.

  - When SecureCRT standalone was installed, changing the protocol
    for a saved session resulted in a crash.

  - Under particular circumstances, if a remote system sent a
    character that was out of range for an escape sequence, SecureCRT
    may have stopped displaying data sent by the remote.

  - When personal configuration data was stored separately, creating
    a new Default.ini file or importing new sessions may have caused
    the personal data to be overwritten.

  - When importing sessions from an XML file, the session options
    not specified in the XML file did not inherit from the Default
    session as expected.

  - When opening a saved session from the SecureCRT command line,
    if additional command-line arguments were specified (e.g.,
    username), those arguments were saved to the specified session.

  - If the Command Manager folders were manually re-ordered, the
    folder order reverted back to alphabetical after restarting
    SecureCRT.

  - When using TVI910 or TVI925 emulation, SecureCRT was not handling
    the "Erase page" or "Erase line" escape sequences.

  - When the prompt send delay option was configured and bracketed
    paste was supported by the remote system, the prompt send delay
    did not work as expected.

  - When the "Show Session Manager or Connect dialog on startup"
    option was enabled and there were no saved sessions, the
    Session Manager or Connect dialog were not shown at startup.

  - When both trace options and session logging were enabled,
    disconnect messages displayed in trace output were not logged
    to the session log file.

  - When connecting to a session with public-key authentication
    enabled, no key file specified, and the "Display logon prompts
    in terminal window" option set, an unexpected warning message
    regarding the private key was displayed in the terminal view.

  - When the license data copied to the clipboard stripped the
    newlines (i.e., license data was on a single line), the License
    wizard was not able to parse the data.

  - When prompted with certain SSH1/SSH2 host key acceptance dialogs,
    the text on the dialog may have been malformatted.

  - When using the New Session wizard to create a session, the
    firewall dropdown listed each configured firewall twice.

  - If a new credential was added when adding a Credentials button,
    the new button did not appear on the button bar until after
    SecureCRT was restarted.

  - Windows: SecureCRT crashed when opening a Scratchpad tab if the
    default terminal protocol was set to None.

  - Windows: Scratchpad tabs did not open as auto sessions if the
    default terminal protocol was set to None.

  - Windows: When the display scaling was set to certain values
    (e.g., 175% or 225%) and a custom menu/toolbar file was in use
    that included non-square icon images, SecureCRT could have
    crashed at startup.

  - Windows: When applying a license from the command-line tools
    vsh, vsftp, vcp, or vpka using the "--license" command-line
    option, if the License wizard was cancelled after entering
    the license data, a crash occurred.

  - Windows: With FIPS mode enabled, attempting to change an RSA
    private key passphrase failed.

  - Windows: If an RDP connection was interrupted by a network
    disconnect, the RDP session could not be reconnected after the
    network connection was reestablished.

  - Windows: When a SecureCRT window was shared within a Microsoft
    Teams meeting, certain actions could cause the window to appear
    frozen to the meeting attendants.

  - Windows: The SecureCRT application window could have been
    displayed off screen if the system display settings were changed.

  - Windows: If the "Preserve window size when opening sessions"
    global option was set, cloning a session in a new window may
    have resulted in the new window opening smaller than expected.

  - Windows: When the Session Manager, Command Manager, or Active
    Sessions Manager was docked and visible, then toggled off, the
    terminal view size may have unexpectedly increased.

  - Windows: When toggling the vertical scroll bar off and on, the
    terminal view column size may have unexpectedly increased.

  - Windows: When focus was in the Connect Bar and the Enter key was
    pressed without entering a hostname or session, a connection was
    attempted using the "<Alt + R>" hint text as the hostname.

  - Windows:  When using a mouse double-click to start a selection,
    that selection could not be expanded outside of the current
    terminal view.

  - Windows: If focus was moved to another SecureCRT window via a
    MENU_WINDOW_* function and the other window was displaying a
    dialog (e.g., Enter Password dialog), focus was not placed
    in the dialog.

  - Windows: When SecureCRT started, the Button Bar selection dropdown
    could have appeared wider than necessary.

  - Windows: When the Enter key was pressed to connect to a session
    or host from the Connect Bar, a bell sound was unexpectedly
    played.

  - Windows: If a matched keyword highlighting word wrapped across a
    line and the word was changed such that it no longer matched, the
    highlighting was not cleared from the first line.

  - Windows: When inactive window transparency was enabled and focus
    was outside of the terminal view when the SecureCRT window became
    inactive, the transparency setting was not applied.

  - Windows: After starting SecureCRT, the "Manage Agent Keys" menu
    item was unexpectedly disabled.

  - Windows: When launching the Connect dialog from a docked
    SecureCRT taskbar icon, then choosing to open a session in
    SecureFX, both SecureCRT and SecureFX opened.

  - Windows: On Windows 11, the application window did not have
    rounded corners when the "VS2013 Blue", "VS2013 Dark", or
    "Office 2013" display theme was selected.

  - Windows: When an SSH2 session was connected, the protocol
    information displayed on the status bar may have been cut off.

  - Windows: When SecureCRT and SecureFX were integrated and the
    terminal protocol was changed to one that does not allow a file
    transfer protocol to be set, the file transfer pages may not have
    been hidden.

  - Windows: If the system text size was increased, the text
    displayed on various dialogs was not scaled as expected.

  - Windows: When navigating the Firewall selection dropdown via the
    keyboard, when the "Select Session..." option was highlighted,
    the Select Session dialog was automatically opened.

  - Windows: If a session name started with the same characters as
    a named firewall (e.g., "test" and "test_firewall") and that
    session was selected as the firewall, the firewall setting
    displayed the wrong name.

  - Windows: On some dialogs, the label was not displayed when the
    mouse hovered over a button.

  - Windows: When a Local Shell, RDP, or Scratchpad session was
    opened, the titlebar did not include the application name.

  - Windows: Importing from an XML file failed silently if an
    imported session's name contained illegal characters.

  - Windows: When using the OpenSSH agent, if an error occurred when 
    a key was added to the agent, the error message may not have been
    displayed as expected.

  - Mac: When certain data was displayed on the screen and the window
    was resized, SecureCRT could have crashed.

  - Mac: When updating the applications using "Update Now", if
    elevating to an administrator account was required, the
    installation of the new version may have failed.

  - Mac: When SecureCRT was moved to an external monitor or a
    virtual desktop space, the Button Bar selection dropdown menu
    may have appeared on the wrong display.

  - Mac: When transferring a file over Zmodem within a local shell
    session, the terminal could have ended up in an unusable state.

  - Mac: When a file was dragged from Finder into SecureCRT, if
    the file contained parentheses, they were not escaped.

  - Mac: If a session was connected before dismissing the beta
    expiration warning dialog, the dialog could not be dismissed.

  - Mac: When the system color mode changed from Light to Dark or
    Dark to Light, the color of some items in the Global and
    Session Options dialogs did not update.

  - Mac: Bold text appeared fuzzy with some fonts.

  - Mac: When using the "Monaspace Neon Var" font, the "Regular"
    font weight did not appear in the style list.

  - Mac: The SecureCRT icon appeared blurry on some Retina displays
    when using Command+Tab to switch applications.

  - Mac/Linux: When connecting to a session that had an IP address
    specified for the hostname, an unnecessary name lookup was
    performed on the IP, which could result in the connection
    failing.

  - Mac/Linux: When opening SecureFX from a connected SecureCRT
    session tab, the session did not open after SecureFX launched.

  - Mac/Linux: Sensitive data related to font and shell command
    settings was not included in the personal data folder. 

  - Mac/Linux: When the Serial protocol was selected in the Quick
    Connect dialog and the serial port was cleared, the Connect
    button remained enabled.

  - Mac/Linux: If focus was in one SecureCRT window while another
    SecureCRT window was running a script that was connecting
    sessions, focus unexpectedly moved to the script window.

  - Linux: When specifying a custom baud rate, SecureCRT may not
    have used the baud rate and no errors were logged. 

  - Linux: If a session had a multi-line description, when the mouse
    hovered over the session tab, the tooltip was partially obscured
    by the system cursor when the cursor was set to a large size. 

  - Linux: The Help button in the Connect dialog could not be
    pressed.

  - Linux: The toolbar in the Synchronize tab appeared larger than
    the main window's toolbar.
