SecureCRT(R) 9.1 (Official) -- September 2, 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.1 (Official) -- September 2, 2021
--------------------------------------------------------
No changes.
Changes in SecureCRT 9.1 (Beta 5) -- August 24, 2021
----------------------------------------------------
Bug Fixes:
- Attempting to connect multiple sessions that used the same Python
logon script could have caused SecureCRT to crash.
- When multiple sessions were reconnecting simultaneously, SecureCRT
could have crashed.
- When attempting to connect a session configured to use the HID
Global ActivClient PKCS11 DLL to access a certificate on a smart
card, authentication may have failed due to a signature error.
- When connected to an SSH1 server, the cipher algorithm used for
the connection was not displayed on the status bar.
- Windows: The Active Sessions Manager context menu was not shown
when the "context menu" keyboard key was pressed.
- Mac/Linux: Undocking a docked Session Manager or Command Manager
by double clicking it caused the terminal area to shrink.
Changes in SecureCRT 9.1 (Beta 4) -- August 10, 2021
----------------------------------------------------
Change:
- Added a parameter to the Screen Object Send method that specifies
whether or not to use a codec when sending the text only to the
screen.
Bug Fixes:
- When extended ASCII line-drawing characters were sent directly to
the screen from a script, the characters were not rendered
correctly.
- Windows: If a session failed to connect, the incorrect status icon
would have been displayed for the session in the Active Sessions
Manager.
- Windows: When using the "Tile Vertically" or "Tile Horizontally"
window layout, if the Command Window was toggled on or off, the
session windows did not resize as expected.
- Mac/Linux: Undocking a docked Session Manager or Command Manager
by double clicking it caused the terminal area to shrink.
Changes in SecureCRT 9.1 (Beta 3) -- July 22, 2021
--------------------------------------------------
Changes:
- Improved transfer speed when port forwarding SFTP traffic
through SecureCRT.
- The "ESC z ( msg CR" instruction to set the status text for
WYSE50 emulation is now honored.
- Windows: In the Active Sessions Manager, the "Sessions"
subfolder was removed and the open sessions are located
directly in the "Active" folder.
Bug Fixes:
- If prompted to accept a new host key at the same time that
the connection was aborted, a crash could have occurred.
- When running a script that accessed a global configuration
option, the script may have failed.
- When transferring large files via YModem, the reported time to
transfer the file was not accurate.
- Windows: When running a Python script that modified the Global
configuration, SecureCRT could have potentially crashed when
the application was closed.
- Windows: If a remote server did not support the RDP view resize
method used by the client, there could have been long delays,
during which SecureCRT became unresponsive, when the SecureCRT
window was resized.
- Windows: Under certain scenarios, when closing and re-opening
the Active Sessions Manager, the width of the Manager may not
have been correct.
- Windows: When using tiled windows for connected sessions, the
tiled window frame did not honor the color for certain display
themes.
- Windows: When using the Connect Dialog, the copy and paste
keyboard shortcuts (CTRL+C and CTRL+V) failed to work when
focus was in the search filter box.
- Windows: If a "Custom menu and toolbar" file was configured to
use either the default.mnu or Japanese.mnu files that are
shipped with SecureCRT, a warning dialog appeared at startup
regarding an unknown command string in the menu file.
- Windows: In certain scenarios, when focus was given to
SecureCRT, background colors in the terminal view may have
unexpectedly expanded across the entire view width.
- Windows: If an error occurred while attempting to update the
application using "Update now...", the error message may not
have been displayed as expected.
- Mac/Linux: When connecting a session that was configured to use
the "Scale the font" resize method, if an existing disconnected
tab was re-used for the new connection, the size of the window
would unexpectedly shrink.
- Mac/Linux: When running SecureCRT and SecureFX integrated, if
one application was launched from the other, after navigating
to the "Configuration Paths" category in the Global Options
dialog, it was not possible to navigate to a different category.
- Mac/Linux: If a disconnected tab was reused by a different
session, the new session may have incorrectly used the color
scheme of the disconnected session.
- Mac/Linux: When running SecureCRT and SecureFX integrated and
the HTTPS session protocol page was displayed in SecureCRT, the
username and password field labels were not displayed correctly.
- Mac/Linux: When changing the location of a docked Session
Manager or Command Manager window while a session was connected,
the size of the session could have unexpectedly changed.
- Mac/Linux: When copying a Button Bar to the Command Manager, if
the Button Bar contained an operation that was invalid for the
current platform, the Button Bar was not copied as expected.
- Mac: If multiple virtual desktops were set up using Spaces and
SecureCRT was running on one of the virtual desktops, if
SecureCRT was moved to an external monitor, the Session Manager
and dialogs were displayed on the primary monitor.
- Mac: The VanDyke Update dialogs did not honor the system Dark
Mode setting.
Changes in SecureCRT 9.1 (Beta 2) -- June 29, 2021
--------------------------------------------------
Bug Fixes:
- Under rare circumstances, when multiple sessions were connected
and the window was resized (causing rows with long lines to
re-wrap), SecureCRT could have crashed.
- In rare circumstances, when sending a session tab to a new window,
SecureCRT could have crashed.
- Windows: When a Python 3 DLL was found on the system, but could
not be loaded, SecureCRT may have failed to start.
- Mac/Linux: Using the filter search in the Command Manager could
have resulted in long delays when there were a large number of
commands to filter.
- Mac: When SecureCRT was in full screen mode and a session was
connected, the session view may not have filled the available
space of the main window.
Changes in SecureCRT 9.1 (Beta 1) -- June 3, 2021
-------------------------------------------------
New Features:
- Windows: Added a dockable Active Sessions Manager that shows
the currently open tabbed or tiled sessions.
- Mac: Added support for Big Sur.
- Added support for Python 3.9.
- Added OpenSSH Agent support for the rsa-sha2-256 and rsa-sha2-512
signature formats.
- Added the ability to close all tabs to the right of the
current tab.
- Added the ability to open a local shell automatically when
SecureCRT starts.
- The Command window's foreground and background colors can be
specified.
- Improved the look of the button bar and Command Manager icons.
- Added the ability to bypass the firewall settings for SSH1, SSH2,
and Telnet sessions globally from the Options menu.
- The status bar can be configured to show the TFTP server status.
- Added a session option to include a timestamp on each line of
the log file.
- Windows: Added the ability to redirect local drives for RDP
sessions.
- Windows: Added the ability to specify an initial folder for
local shell sessions.
- Windows: A scratchpad can be configured as an auto session to be
opened when SecureCRT starts.
- Windows: Added the ability to change the foreground and
background colors for scratchpads and script editors.
- Windows: Added the ability to change the font for scratchpads
and script editors.
- Windows: Added the ability to specify initial values of "Line
numbers" and "Word wrap" options for scratchpads and script
editors.
- Mac: Updated the GUI by removing the toolbar and moving the
toolbar items to the title bar.
Changes:
- The log file trace level can now be specified in the Session
Options dialog.
- The reconnect time interval can now be specified in the
Global Options dialog.
- Windows: For all display themes, the title bar now uses the
standard Windows Minimize, Restore, and Close buttons and uses
the system accent color if the Windows Colors option "Title bars
and window borders" is set.
- Windows: The global options "Paste on left/right button" and
"Copy on select" are honored in the scratchpad and script
editor.
Bug Fixes:
- If a session displayed in the Session Manager was no longer
available on disk, operations (e.g., copy, rename) on the session
could have resulted in a crash.
- Under certain configurations, when SecureCRT was maximized or
full screen, if the "screen" utility was run on a remote system,
the current display was not completely cleared as expected.
- When switching from TN3270 to any other emulation, an
"IBM-3278-2" terminal type may have been unexpectedly set
for the session.
- Windows: Under rare circumstances, if an RDP session was closed
while the main window was resizing or moving, SecureCRT could
crash.
- Windows: If an RDP session was closed before the connection was
fully established, SecureCRT could have crashed.
- Windows: Under certain environments, when connecting to an RDP
session, the remote display did not scale to match the local
desktop.
- Windows: When using a Windows Subsystem for Linux provided local
shell (e.g., bash.exe, wsl.exe), clearing the screen did not
always work as expected.
- Windows: When the global INI-file-only option "Launch New Windows
in a Separate Process" was set, it was still possible to select
"Clone in New Window" or "Send to New Window" from the tab or tile
context menu.
- Windows: On high-DPI monitors with certain scaling levels, the
MD5 fingerprint displayed on the view host key dialog may have
been cut off.
- Mac/Linux: Under certain conditions, using Zmodem to upload a
file that already existed on the remote system could have
resulted in a crash.
- Mac/Linux: If the log filename or custom log data fields
included a newline in the specified value, the options were not
saved correctly.
- Mac: When using a trackpad on a macOS system, certain gestures
could result in focus being lost in the SecureCRT terminal view.
