SecureCRT(R) 9.2.2 (Official) -- June 16, 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.2.2 (Official) -- June 16, 2022 ------------------------------------------------------ Bug Fixes: - If a saved credential was modified while editing multiple sessions simultaneously, SecureCRT could have crashed. - When a newly generated public key was saved in OpenSSH format, the key could not be used for authentication due to an incorrect file format error. - When editing multiple sessions at once, the port field could not be changed. - When using the "Personal data folder" option, if a session option was modified, the personal data store options could have been saved to the non-personal configuration. - If multiple sessions were connected in tab groups, zooming the font in one tab group could have caused the font zoom to be reset in another tab group. - Windows: If multiple RDP sessions were connected and the "Close on disconnect" session option was enabled, closing the main window could have resulted in a crash on exit. - Windows: When the "Make SecureCRT the Default Application" button was pressed, SecureCRT was not set as the default application for SSH or Telnet URLs. - Windows: When the confirm disconnect option was enabled and an RDP session was connected, closing the application resulted in multiple confirm disconnect prompts. - Windows: When using the Microsoft Pinyin Input Method Editor to enter Chinese characters in fields that contained hint text (e.g., Session Manager filter field), the hint text was not cleared when the Chinese characters were entered. - Mac: If SecureCRT crashed and the user chose to report the crash, the email template used for the report may not have contained the correct version of SecureCRT. - Mac/Linux: If the main window was closed while in full-screen mode with a session connected, the next time that session was opened, the window did not return to full screen mode. Changes in SecureCRT 9.2.1 (Official) -- May 12, 2022 ----------------------------------------------------- Bug Fixes: - If the Button Manager dialog was launched from the Button Bar Manager dialog, changes to the buttons were not saved. - Windows: When connecting to a server that uses an X.509 certificate for the host key, even though the certificate met all requirements for automatic acceptance of the host key by the client, the application still prompted the user to manually accept and save the key. - Windows: When RDP or Local Shell sessions were exported and later imported to a different configuration, the protocol-specific options may not have been preserved as expected. - Windows: In certain cases, when moving focus from the hostname field to the port field using the tab key, the text contained within the port field was not selected. - Mac: When selecting a file to transfer via the "Send ASCII..." functionality, the file browse dialog was restricted to ".txt" file extensions and did not include a file type filter field to allow other file types. Changes in SecureCRT 9.2 (Official) -- April 26, 2022 ----------------------------------------------------- Bug Fix: - On certain systems, when clicking on some web links displayed in the application, the expected page may not have been displayed in the web browser. Changes in SecureCRT 9.2 (Beta 5) -- April 19, 2022 --------------------------------------------------- Changes: - In the About box and other dialogs that contain hyperlinks, it is now possible to tab to the hyperlink, which allows the links to be read by screen reader software. - When the Quick Connect dialog box is opened, focus is placed in the Protocol dropdown list. This change was made for Section 508 (accessibility) compliance on Windows. - Windows: The hint that is displayed in the Connect bar and filter bars for the Session, Command, and Active Sessions managers remains visible until the user starts typing. - Mac: The About box shows the architecture type (x64 or ARM64) of the application. Bug Fixes: - If the %I (IP address) substitution variable was specified for the session tab label and the remote system sent a title change request, the variable was not expanded, resulting in the tab displaying the literal "%I" string. - Windows: If the JAWS screen reader was closed while SecureCRT was running, SecureCRT crashed. - Windows: When a session tab's closing resulted in another open tab receiving focus, the title bar continued to display the name from the closed tab. - Windows: In the Session Options dialog, in the Port Forwarding and Remote Port Forwarding categories, hovering over a port forward in the list selected it. - Mac: When connecting to multiple sessions in which the configured firewall was not found, the "Firewall not found" warning message could get into a state where it could not be closed, causing the application window to become unusable. - Mac: Under certain scenarios, when clicking on the Dock icon for a running instance of SecureCRT, a new instance of the application was launched instead of giving focus to the existing instance. - Mac: If the window transparency slider for either the active or inactive window was set to certain non-default values, when the Global Options dialog was re-opened, the slider position for both active and inactive windows was moved. Changes in SecureCRT 9.2 (Beta 4) -- March 31, 2022 --------------------------------------------------- Bug Fixes: - When a saved credential was changed for a disconnected session, SecureCRT could have crashed when the session was reconnected. - When the window was resized and the terminal view contained a very long line that spanned multiple rows, SecureCRT could crash. - When using the "Retain size and font" session resize option, the "Select all" menu option failed to select any text in the terminal view. - When there were a large number of folders in the Session Manager or Command Manager, using the "Expand All Folders" or "Collapse All Folders" options could have taken a long time to complete. - When using the "Personal data folder" configuration option, the reference to a saved credential used by a session was stored in the common session configuration file. - When a session tab that did not have focus received new input, the title bar for a session tab that did have focus could have been unexpectedly updated. - Windows: When a session tab received focus due to another tab closing, the tab status indicator did not update to the current state. - Windows: If the Session Manager was toggled between auto-hidden and pinned mode (or vice-versa), the SecureCRT main window may not have resized as expected. - Windows/Linux: When opening the session window Find dialog after the SecureCRT window had been moved, the dialog opened relative to the previous SecureCRT window location. - Mac/Linux: If a session tab closed while a script dialog was displayed, SecureCRT could have crashed. - Mac/Linux: If the "Alt+<#>" tab switching keyboard shortcut was sent from the Command Window when there were no open tabs, SecureCRT crashed. - Mac/Linux: When using the Quick Connect dialog to connect to a host, the username and credential settings were not preserved between uses. - Mac: Under certain circumstances, clicking on the SecureCRT menu items would not have resulted in the menu opening as expected. - Mac: When connecting a session in which the configured firewall cannot be found, the "Firewall not found" warning message could get into a state where it could not be closed, causing the SecureCRT window to become unusable. - Mac: Under certain circumstances, clicking on a session or folder in the Session Manager did not immediately move focus to that session or folder. - Mac: When Python was installed via Homebrew on an M1 system, SecureCRT did not load the Python engine at startup. Changes in SecureCRT 9.2 (Beta 3) -- March 3, 2022 -------------------------------------------------- New Feature: - In the Session Options dialog, Quick Connect, and New Session Wizard, if a string like "user@host:port" is entered as the username, it is parsed and the values are placed in the appropriate fields. Changes: - When connecting to a session that uses saved credentials, if the credentials are not valid, the dialog that prompts for the credentials has an option to specify whether or not the saved credentials should be updated. Bug Fixes: - If a session tab was closed while certain dialogs (i.e., Session Options or multi-line paste confirmation) were displayed, SecureCRT could have crashed. - If a Button Bar button or Command Manager command was configured with a Send String that contained certain character patterns, the Send String was truncated when SecureCRT restarted. - When a script called the WaitForKey method, scrolling performance degraded significantly. - When running a script that changed a session configuration option, the keyword highlighting settings were re-applied to the view even if the option changed did not affect keyword highlighting. If there was a large keyword highlighting list in use with a large scrollback buffer, this could have caused a long delay during which SecureCRT was unresponsive. - When using the "Personal data folder" option, changes made to an option (e.g., username or password) stored in the personal configuration caused the non-personal configuration file to be written to disk. - Windows: Under certain scenarios, if the SSH2 protocol was not installed, SecureCRT could crash at startup. - Windows: If a session tab closed while a script dialog was displayed, SecureCRT could crash. - Windows: If the Find dialog was displayed when a session was closed, SecureCRT could have crashed the next time the session connected. - Mac: Under rare circumstances, certain text fields within the New Session Wizard stopped accepting input. - Mac: If the configuration directory was a Google Drive synchronized folder or a SAMBA share, changes (including creating, copying, and renaming sessions) to the configuration failed. - Mac: If SecureCRT was running and displayed on an external monitor while that monitor was disconnected and later reconnected, the SecureCRT window did not automatically return to the external monitor. Changes in SecureCRT 9.2 (Beta 2) -- February 3, 2022 ----------------------------------------------------- New Features: - Added a substitution parameter "%e" for inserting newlines in custom log data. - Windows/Mac: Added support for Python 3.10. Changes: - Added the ability to used saved credentials when creating an SSH2 or RDP session with the New Session Wizard. - For SSH2 sessions, saved credentials can be specified on the command line or in the Connect bar with the "/CREDENTIALS" option. This option can also be used with RDP sessions on Windows. - Added the ability to access the Manage Saved Credentials dialog from the Tools menu. - The full path of the destination file is now displayed in the Export Settings output. - Windows: Added a scratchpad icon for the "Open Scratchpad" menu item, which can be used when customizing the toolbar. - Windows: The RDP session options password field now obfuscates the number of characters the password contains. Bug Fixes: - In rare circumstances, if the active Button Bar was changed while a button edit was in progress, SecureCRT could have crashed. - Under rare circumstances, toggling the color mode and/or the "Use color scheme" option while running a remote application that uses an alternate screen could have resulted in a crash. - If the default session had a saved credential specified, creating a new credential could have resulted in a crash. - If the default session was configured to use a set of saved credentials, adding a new set of credentials could have resulted in all other saved credentials being modified with the settings from the new set of credentials. - Saved credentials were not stored in the correct location when the personal data folder option was toggled. - If the Public Key Properties dialog was opened and closed when a new set of saved credentials was being added, the credentials were prematurely saved, which resulted in a error being reported when the credentials were explicitly saved by closing the dialog. - When connected to a remote system with shell support for bracketed paste mode, commands sent from the Command Window were not immediately executed as expected. - Windows: When the "Remember and connect to sessions from last use" option was enabled and one or more of those sessions were unavailable, SecureCRT could have crashed at startup. - Windows: If a script file was opened for editing, the opened file behaved as if a default scratchpad tab was opened. - Windows: If the application loaded license data from a license file, a non-administrator was not able to update the license via the License Wizard. - Windows: If password saving was disallowed by an administrative policy, the password specified on the command line for an ad hoc connection was not used. - Mac/Linux: After creating a public key from the Credentials Manager, an offer to upload the key was presented, and if the user chose to upload the key, SecureCRT crashed. - Mac/Linux: When an application was launched as part of a port forward configuration and the path to the application contained a space, the application did not launch as expected. Changes in SecureCRT 9.2 (Beta 1) -- January 4, 2022 ---------------------------------------------------- New Features: - Added a Credentials Manager that allows SSH2 authentication credentials to be saved and used for multiple sessions, which makes it easier to change saved passwords or other credentials. On Windows, RDP authentication credentials can also be saved. - Mac/Linux: Added a dockable Active Sessions Manager that shows the currently open tabbed or tiled sessions. - Added the ability to import sessions from CSV, TSV, or other delimited text files. - Windows: A new option allows the contents of the scratchpad to be saved automatically and reloaded when SecureCRT restarts. - The mouse wheel can be used to scroll the tabs in the tab bar when the sessions don't all fit. - SSH2: When attempting an SSH2 connection, if the Cipher or MAC algorithm negotiation fails, SecureCRT offers to enable a supported algorithm and try again. - SSH2: Added the ability to use PPK3 files for public-key authentication. - SSH2: Added support for PPK keys that use the -cert-v01@openssh algorithm. - Windows: Added the ability to temporarily rename a window, which makes it easier to locate a specific SecureCRT window from the Windows taskbar when there are multiple instances running. Changes: - Windows: Improved the terminal output scrolling speed. - Windows: In FIPS mode, digital signatures that use SHA-1 as the hashing algorithm can no longer be used because they are not allowed by the upgraded version of the FIPS library module. - For newly-generated RSA host keys, the minimum size is now 1024 bits. - Modified the Quick Connect dialog so that the "Show quick connect at startup" option can be saved without having to connect. - Windows: When SecureCRT and SecureFX are integrated, if a scratchpad or script editor is active when SecureFX is launched from SecureCRT, SecureFX will not attempt a connection. - Windows: The "Connect in Tab/Tile" icon is shown in the File menu and can be used when customizing the toolbar. - Windows: It was not possible to customize the toolbar when more than one session was open. Bug Fixes: - When generating an SSH1 RSA key pair that was larger that 2048 bits, SecureCRT crashed. - Attempting to use an ecdsa-sk or ed25519-sk type public key resulted in a crash. - When connecting to a session that had auto-reconnect enabled, if the dialog that offers to enable a common Key Exchange, Cipher, or MAC algorithm was displayed, the dialogs would continually stack on each reconnect attempt, which could have eventually lead to a crash. - If the configuration was located on a network share, using the session filter search within the Session Manager could have caused a momentary hang. - When authenticating with a 512-bit RSA key, if the rsa-sha2-512 signature algorithm was used, authentication failed. - The menu items "Disconnect All" and "Reconnect All" didn't work with RDP sessions. - When the OSC 52 escape sequence was received without the "c" parameter specified, the included text was not copied to the clipboard. - Under certain scenarios, firewall name changes were not immediately reflected in the Session Options dialog for sessions that used the firewall. - When setting a session tab label from a script, the title bar label was not updated until focus was moved away from and back to the SecureCRT window. - If a Putty-generated private-key file (.ppk format) was specified as the session public-key file, the "Upload" button was unexpectedly disabled. - Windows: When SecureCRT was launched from certain network configuration managers and there was an instance of SecureCRT already running which had not been launched from the NCM, SecureCRT could have crashed. - Windows: When authenticating with an OpenSSH Trusted Certificate, if the private key was in the agent, authentication failed. - Windows: If the application was under heavy load, drop down and context menus could be slow to display. - Windows: When connected to an RDP session, if the context menu keyboard key was pressed while focus was in the RDP view, the context menu for the SecureCRT main window was unexpectedly displayed. - Windows: If the Session Manager and Command Manager were docked above and below the Button Bar, the main window could unexpectedly resize when moved. - Windows: When multiple SecureCRT windows were open and one of the windows was minimized, certain actions could have caused the terminal view of the minimized window to have the wrong size and display a white background in part of the view. - Windows: On certain option fields that could display a horizontal scroll bar (e.g., Global\SSH2 Fingerprint field), if the display was scaled above 100%, the scroll space was not calculated correctly. - Mac/Linux: When connecting to a host via QuickConnect, if the "Get username from certificate" public key option was enabled, the username field did not reflect that the username would be provided by the configured certificate. - Mac/Linux: If the Session Manager and Command Manager were docked adjacent to each other and one of the managers was closed or re-positioned, the terminal view could unexpectedly shrink in size. - Mac/Linux: When a docked Session Manager or Command Manager was moved from the left/right edge to the top/bottom edge or vice versa, the height or width (respectively) increased by a few pixels. - Mac/Linux: When the Session, Command, and Active Sessions Managers were docked and auto-hidden on either side of the window, the window could not be re-sized to be smaller than the space required to show all three manager tabs. - Mac/Linux: The Command Manager did not dock correctly when the Session Manager and Command Manager were stacked and docked together on the left side of the application window, then they were unpinned, and then the Session Manager was turned off and the Command Manager was re-pinned. - Mac: When dragging a docked Session or Command Manager to a new location, spurious text could have appeared in the drop zone preview rectangle. - Mac: On certain high definition displays, the tab status indicators could appear blurry.