SecureCRT(R) 9.7 (Beta) -- August 28, 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.7 (Beta 2) -- August 28, 2025
----------------------------------------------------
New Features:
- Windows: Added support for the RDP /admin option.
- macOS: Made it is easier to configure SecureCRT as the default
URL handler for ssh://, telnet://, etc. URIs by providing
buttons for doing this in the Global Options dialog.
Changes:
- Added the ability to map a button, command, or key to the Session
Manager's manual refresh.
- Improved error reporting when a session or folder stored on
OneDrive cannot be deleted by the Session Manager because it is
read-only.
Bug Fixes:
- When applying certain changes from the default session to all other
sessions, a crash may have occurred.
- Certain escape sequences in the fish shell were not displayed
properly.
- When using the block cursor style, the character underneath the
cursor was hidden instead of being shown in reverse video.
- Logon actions were not correctly imported from XML across
different platforms.
- Remote commands configured in a session's logon actions were not
imported correctly from XML across different platforms.
- Windows: If the "Exit when last session is disconnected" option
was enabled and an RDP session tab was closed without
disconnecting, SecureCRT crashed.
- Windows: When there were sessions or folders selected in the
Session Manager, right-clicking on another session or folder
did not clear the original selection.
- macOS/Linux: If a tiled session window was minimized when
switching to tabbed mode, the session window contents were not
displayed correctly.
- macOS: The error dialog produced from invalid command-line
options was dismissed automatically.
Changes in SecureCRT 9.7 (Beta 1) -- August 7, 2025
---------------------------------------------------
New Features:
- Added the ability to save snapshots, which are sets of sessions
and their layout information. This is helpful for setting up
different workspaces depending on the type of work to be done.
- Added a toolbar text box that allows a keyword to be highlighted
temporarily.
- Added support for drag-and-drop SFTP file transfers.
- Added support for the diffie-hellman-group15-sha512 and
diffie-hellman-group17-sha512 key-exchange algorithms.
- Added support for an Xterm R6 alternate keyboard.
- Added support for Xterm 216+ keyboard emulation.
- Added the ability to pause and resume session logging and have
it continue writing to the same file.
- Added the ability to select a conflict resolution method
(overwrite, merge, duplicate, only new) when importing
sessions from an XML file.
- Added the ability to configure default Serial settings
separately from the Default session.
- Added the ability to connect or reconnect an SSH2 session after
changing the username.
- Added the ability to open SSH2 sessions in an SFTP tab without
having to open the SSH2 session first. Sessions can also be
configured to open in an SFTP tab by default.
- The Active Sessions Manager supports multi-select, which allows
operations like disconnect, close, and lock to be performed on
multiple items.
- The Active Sessions Manager indicates the number of open
sessions (all platforms) and editors (Windows only).
- The Active Sessions Manager indicates the currently active
session by bolding the session name.
- Improved zooming performance by making the zoom increment
proportional to the display size.
- Added the ability to map a button, command, or key to send a
string to all connected sessions.
- Added the ability to manually refresh the list of sessions in
the Session Manager.
- Added a "Copy as path" item to the Session Manager's context
menu, which allows a session's path to be placed on the
clipboard.
- Added the ability to specify separate locations for the trusted
OpenSSH certificate and its private key file, which facilitates
compatibility with Teleport.
- Added the ability to always prompt for a set of saved
credentials to use when connecting.
- Saved credentials can be created without a username.
- Added a session option to suppress the trailing CR in logon
actions.
- Added a global INI-file-only option "Vertical Line Padding" that
allows the spacing between lines of output to be configured.
- Added the ability to deregister SecureCRT, making it easier to
move a license to a different machine.
- Windows: Added support for Python 3.14 scripts.
- Windows: Added an administrative option that disallows public
key creation.
- macOS/Ubuntu: Added an Auto Hide icon to the Session, Command,
and Active Session managers.
Changes:
- For new installations of SecureCRT, the default cipher is
aes256-gcm@openssh.com.
- SecureCRT skips the x509v3-rsa2048-sha256 signing algorithm
when connecting to sessions using the Cisco compatibility mode.
- When selecting text in a session, scrolling speed is increased
as the mouse cursor is moved outside the scrolling area.
- If a session doing keyword highlighting contains a selection
that could be a valid keyword, the keyword can be added via the
Options menu.
- Added the ability to access the Keyword List Properties dialog
from the Options menu.
- Added the ability to map a key, button, or command that opens
the Keyword List Properties dialog.
- If the "Show confirm disconnect dialog" or "Confirm when closing
multiple tabbed or tiled sessions" option is set, only one
confirmation prompt will be displayed when closing multiple
sessions at the same time.
- When duplicating a session, the port can be modified.
- The Session Manager's find session options are now saved.
- Changed the status indicator icon for a locked session to appear
as an overlay over the existing icon.
- Added "Connect SFTP Session" to the Active Sessions Manager's
right-click menu.
- In the Active Sessions Manager, the "Active" folder is now
called "Sessions".
- In TN3270 emulation, pressing the backspace key performs a
destructive backspace instead of moving the cursor to the left.
- XML imports warn if the license being imported isn't valid for
the current version of SecureCRT. Invalid and trial licenses
are not imported.
- The XML import log includes the serial number of an imported
license.
- The "Select SSH2 Session" now remembers the last selected
firewall session.
- In the Global and Session Options dialogs, if column widths in
tables are adjusted, these changes are saved.
- The Firewall Properties dialog can be resized.
- Added a Friendly Name column to the Select Certificate dialog.
- The product version is displayed at the top of the "Enter
Passphrase" and "Change or Reset Passsphrase" dialogs.
- Windows: Updated some of the display themes.
- Windows: RDP sessions can be reconnected without having to be
disconnected first.
- Windows: Made GUI for locking sessions and editors consistent
with each other.
- Windows: In the Active Sessions Manager, the Editors folder
is now at the same level as the sessions folder.
Bug Fixes:
- ECDSA keys generated by SecureCRT and saved in OpenSSH format
may not have been usable by OpenSSH clients.
- Generated keys saved in the OpenSSH format were saved with
Windows line endings, leading to compatibility issues with
some tools, such as SSHFS-WIN.
- When connecting to a server that advertised the supported public-
key algorithms via the server-sig-algs extension, authentication
may have attempted to use a public-key algorithm that the server
did not support.
- When a session prompted for saved credentials as part of the
initial connection, the saved credentials were not used if
the session was reconnected.
- Automated logon actions configured for a session were not sent
correctly if the session was used as a firewall.
- The session option "Disable resize" only locked the size of the
window, not the number of rows and columns in the session view.
- If session logging was started before a session was connected,
custom log data specified for the session was not logged.
- When mapping a menu function to a key, command, or button, the
Lookup Selection, Use Firewall, and Rename Window menu items
were not available.
- When a session was closed from the Active Sessions Manager, focus
moved back to the session view instead of remaining in the Active
Sessions Manager.
- The option "Only show tabs when there are more than one" was
not honored for tab groups.
- Changes made to session keyword highlighting were not applied
while scrolled up into the session history.
- Changes made to the default session were saved even when the
"Apply default session changes" dialog was canceled.
- Some Default Session options were not being honored in Quick
Connect.
- Auto sessions saved with the "Remember and connect to sessions
from last use" option did not restore SSH2 sessions with the
"SFTP session" option.
- Subfolders created in the Session manager were not immediately
propagated between open instances of SecureCRT.
- When a session file was deleted from the file system, attempting
to delete that same session from the Session Manager resulted
in an error.
- The escape sequences ESC[=;u, ESC[=u, and
ESC]133;A;BEL were not being processed, causing extraneous
information to be displayed. These escape sequences are now
processed but ignored.
- When SecureCRT was launched using the /Session_Folder command-line
option with the top-level folder specified, connection attempts
were made to the default session profiles.
- A failed SFTP file transfer from an SSH2 session could cause a
small memory leak.
- Windows: Attempting to connect a newly copied transfer session
could have caused SecureCRT to hang.
- Windows: SecureCRT did not export the public key into an SSH2 key
even if "Use certificate as raw SSH2 key" was enabled.
- Windows: If a public key in the session options contained
"%USERPROFILE%" in the path, SecureCRT failed to find the
associated private key.
- Windows: If an execute escape sequence operated on a filename
or path that included Unicode characters, the escape sequence
may have failed.
- Windows: When TLS 1.3 was used for an FTPS or HTTPS connection,
the negotiated key exchange algorithm was incorrectly logged as
"CN" with a strength of 0.
- Windows: When a tiled session window was minimized, the remaining
tiled windows were not resized to fill the available space.
- Windows: When connecting to an RDP session that had the raw
logging option enabled, CPU usage increased to 100%.
- Windows: When connecting an RDP session in a tab group, the size
of the view may not have been correct.
- Windows: When in tiled window mode, if an RDP session was
opened, the connection status indicators did not update to show
the session's current connection state.
- Windows: When importing a configuration, if both a folder name and
session name were part of the same "key name=" line, the session
was not imported as expected.
- 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: When hovering over items in the button bar context menu
the status bar displayed incorrect help text or no help text.
- Windows: When pressing CTRL+TAB to cycle through the open
session tabs, the list of sessions in the Active Sessions
Manager could have appeared empty while the tabs were being
cycled.
- Windows: If the Connect Dialog was resized too small, after
increasing the size, the controls were not drawn correctly.
- Windows: Incorrect icons could have been displayed in the Window
menu when SecureCRT was running in the same process as SecureFX.
- macOS/Ubuntu: In the Session Options dialog, changes made to the
username could have been reverted by selecting the PublicKey
authentication option after making the change.
- macOS/Ubuntu: When session windows were tiled horizontally or
vertically and one of the windows was minimized, the window
mode switched to cascaded.
- macOS/Ubuntu: The mouse cursor was not hidden when typing in the
Command window.
- macOS: When connected to terminal sessions, scrolling speeds
may have been slower than expected.
- macOS: Remembered sessions that were closed while in full-screen
mode were not re-opened full screen after restarting SecureCRT.
- macOS: If the SecureCRT window was closed while a session that had
the "Disable Resize" option set was connected, SecureCRT opened
maximized on the next launch.
- macOS: A session's firewall setting could have incorrectly
shown "None" if the global firewall it used was renamed.
- macOS: When the global option "Use Default Session Color On
Startup" was set, SecureCRT did not use the color configured in
the default session.
- macOS: The "Disable Resize" global option was honored, but was
not in the GUI.
- macOS: A file share tab opened from SecureCRT did not bring
SecureFX to the foreground when running in the same process.
- macOS: A small memory leak could occur when a Session Manager
tooltip was displayed.
- macOS: When checking for updates using "Update Now", a small
amount of memory may have been leaked.
- Ubuntu: When running commands in a local shell session, the
command output may not have been displayed.
- Ubuntu: SecureCRT's window re-opened slightly above the position
it was in when it last closed.
- Ubuntu: Tab group dividers were not restored to the correct
position when opening from snapshots or remembered auto
sessions.
