SecureCRT(R) 9.3.1 (Official) -- December 6 , 2022
Copyright (C) 1995-2022 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.3.1 (Official) -- December 6, 2022
---------------------------------------------------------
- When authenticating using an OpenSSH trusted RSA certificate,
authentication failed with OpenSSH version 7.7p1 and earlier.
Changes in SecureCRT 9.3 (Official) -- November 3, 2022
-------------------------------------------------------
Vulnerability addressed:
- An external report claims that when using a brute-force attack,
sensitive data, such as passwords, stored in the SecureCRT or
SecureFX configuration without a configuration passphrase or with
a weak configuration passphrase can be cracked in a relatively
short amount of time. Direct access to the configuration data is
required in order to exploit this vulnerability.
Change:
- Windows: When the command-line utilities are installed with the
SecureCRT standalone installer, the install path is added to
the PATH environment variable.
Changes in SecureCRT 9.3 (Beta 5) -- October 25, 2022
-----------------------------------------------------
Changes:
- Windows: Allow the use of ssh-rsa and ssh-dss algorithms for
signature verification when FIPS mode is enabled.
Bug Fixes:
- When authenticating with a public key that was invalid for the
remote host, the key was retried twice before falling back to
the next authentication method.
- If a session file was renamed or deleted on disk while the
application was running, raising the context menu for the
session from within the Session Manager could have resulted
in a crash.
- If the scrollback buffer size was set to zero, attempting to
extend a text selection into the non-existent scrollback
resulted in a crash.
- When an existing configuration was migrated to the new
encryption standard, Session Logon Actions may have failed to
migrate and could have been reset to default settings.
- Keyword highlighting changes for a connected session were not
applied to the current session view.
- Windows: When connecting to an RDP host from a script and an
invalid credentials file was referenced, the RDP tab could not
be closed.
- Command-line tools: If the host key algorithm preference list
was specified on the command line, the algorithm order was not
always honored.
Changes in SecureCRT 9.3 (Beta 4) -- September 29, 2022
-------------------------------------------------------
Bug Fixes:
- When merging a personal data configuration folder back into the
main configuration, the operation could have failed due to a
mismatch of session files that should have been ignored.
- When SecureCRT was started from the command line with a script
that automatically reconnects the session, an error stating "Only
one script can be run at a time" would be displayed if the session
was disconnected.
- Windows: Under certain circumstances, if a script was cancelled
during a sleep operation, SecureCRT could have crashed once the
sleep operation completed.
- Windows: When running grep with color options enabled on a large
amount of output, the SecureCRT UI could have been slow to respond.
- Windows: When multiple top-level SecureCRT windows were open, if
the Command Window was toggled on in one of the windows, the
right-click context menu could have failed to display in various
locations.
- Windows: If a large number of tabs were open, causing the tab
widths to be truncated, renaming a tab label via a script could
have resulted in the tab size expanding to full width, then
resizing to the correct truncated size.
- Windows: When moving the position of an authentication method
using keyboard shortcuts, if the up or down button became
disabled (due to the method being the topmost or bottom most
position), the dialog itself lost keyboard focus.
Changes in SecureCRT 9.3 (Beta 3) -- August 16, 2022
----------------------------------------------------
Bug Fixes:
- Under certain cases, if a script was cancelled during a sleep
operation, SecureCRT could crash once the sleep completed.
- If the "Preserve window size when opening sessions" option was
enabled, connecting to a session that reused a disconnected tab
caused the window to unexpectedly resize.
- When launching the application with a new configuration, the
Quick Connect dialog was not displayed at startup as expected.
- If there were a large number of tabs open, causing the tab
widths to be truncated, renaming a tab label via a script could
have resulted in the tab size expanding to full width, then
resizing to the correct truncated size.
- When the application license was stored in a license file (.lic)
and the license data was included in a configuration export,
importing the license on another machine may not have worked as
expected.
- Windows: When starting the application using an alternate
configuration path (via the /F command-line option), if the
Global.ini file in the alternate location was incomplete, the
Global.ini file in the default configuration location would have
been reset.
- Mac: When "Scale the font" resize method was configured for a
session, the text displayed in the terminal view could become
unreadable with certain window sizes.
- Mac: On Monterey and later systems, if the application crashed
and produced a core dump, the crash reporter dialog reported that
no core dump was available.
Changes in SecureCRT 9.3 (Beta 2) -- July 19, 2022
--------------------------------------------------
New Feature:
- Windows: The Global Options and Session Options dialogs can be
resized and the size is remembered.
Changes:
- In the Session Options dialog, the column widths for the Keywords
table in the Keyword Highlighting category are remembered.
- The Manage Agent Keys dialog can be resized and the size is
remembered.
Bug Fixes:
- Windows: The Help Search tab did not work.
- Windows: When running a Perl script, setting the Screen object's
IgnoreCase property to true had no effect.
- Windows: When running a Perl script, the IgnoreCase parameter in
the ReadString and WaitForString methods was interpreted as the
timeout parameter.
- Windows: If the "Enable alternate screen switching" option was
disabled while the "Add alternate screen output to scrollback"
sub-option was enabled, the sub-option was shown as enabled after
re-opening the Session Options dialog.
Changes in SecureCRT 9.3 (Beta 1) -- June 28, 2022
--------------------------------------------------
New Features:
- Added an option to check for updates automatically at startup.
- Added the ability to specify saved credentials in "Send" Logon
Actions.
- Added a global option that preserves the application window
size when a session is opened.
- For keyword highlighting, the "Match case" option can now be
specified per keyword. Previously, it could only be specified
for the entire keyword list.
- For keyword highlighting, attributes such as bold and reverse
video can now be specified for individual keywords.
- Added the ability to resize the Keyword List Properties dialog.
- Added an option that forces a prompt for the hostname when the
session connects.
- Added the ability to disable individual local and remote port
forwards.
- Added the ability to duplicate a s