SecureCRT(R) 9.0 (Beta) -- October 20, 2020 Copyright (C) 1995-2020 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.0 (Beta 2) -- October 20, 2020 ----------------------------------------------------- Changes: - On the right-click terminal menu, changed "Google Selection" to "Lookup Selection". The search engine to use for the lookup can be specified in a global INI-file-only option. - Each tabbed session now has it's own font, character encoding, and zoom level. Note: This change was inadvertently omitted from the Beta 1 release notes. - A local shell session can be specified on the command line and in a script by using the /LOCALSHELL command-line parameter. - Windows: Added the ability to rename a scratchpad tab or tile. - Windows: When more than one scratchpad is opened, a number "(n)" is appended to the "scratchpad" tab/tile name. Bug Fixes: - When exporting the configuration to a file, if a folder name was specified instead of a filename, the export file was created using the folder name and the folder itself was renamed with a ".bak" extension. - Dragging a terminal session tab to another SecureCRT window failed if a scratchpad tab had focus in the other window. - When the Xterm "True Color" color mode was enabled, colors were not displayed correctly for certain remote applications (e.g., Aptitude). - The Command window height was not retained if the Command window titlebar was disabled. - When starting SecureCRT from the command line, if the /I option was used to specify the public-key file to use for authentication, it was ignored. - When tab completing an SFTP tab path that contained a backslash character, the path components preceding the backslash were duplicated. - Windows: When JAWS screen reader was running, SecureCRT failed to start. - Windows: SecureCRT was not able to load the Anaconda Python 3.8 script engine. - Windows: When multiple tabs had been opened and the first tab was then closed, the window could no longer be resized. - Windows: On high DPI monitors with certain scaling factors set, the toolbar icons and certain dialog text appeared blurry. - Windows: On systems with a large display scaling factor set (i.e., 300% or greater), the toolbar icons were not displayed correctly. - Windows: When using the "New Session Wizard" to create an RDP session, if the domain was specified as part of the username (i.e., domain\username), the resulting session duplicated the domain (i.e., domain\domain\username). - Windows: When an RDP session was connected to xrdp with "Fit to panel" and "Scaling" options enabled, the reconnect operation that happens when the window is resized failed. - Windows: When RDP was specified as the terminal protocol for the Default session, the RDP options were grayed out and could not be modified. - Windows: When a scratchpad or script editor tab was active, the application titlebar was not updated. - Windows: After saving the contents of a scratchpad tab or tile to a file, the file could not be opened in another application. - Windows: In the "Save As" dialog for the scratchpad, the default filename "scratchpad.txt " contained an extra space. - Windows: Connecting to a session while the main window was maximized and the session window was set to open in cascaded tile mode could have resulted in a blank session window being displayed. - Windows: If the default.mnu file was specified as a custom .MNU file, pressing CTRL+INSERT caused the terminal view to zoom in instead of copying the selected text. - Windows: Under rare circumstances, text in the scrollback was only visible when selected. Changes in SecureCRT 9.0 (Beta 1) -- September 24, 2020 ------------------------------------------------------- New Features: - Windows: Added support for RDP. - Windows: Added support for Python 3. Python 3.8 (available at python.org) must be installed and the script's first line must be: # $language = "python3". Since support for Python 3 is provided through an external module, Python 3 libraries can be used in SecureCRT scripts. - Windows: Added a scratchpad, which has basic editing capabilities, allowing notes to be taken in a tab (or tile). - Windows: Added a script editor with syntax highlighting, which allows local scripts to be edited in a tab (or tile). - Added the ability to specify public/private keys to load into SSH2 agent when SecureCRT starts. - The status bar has been enhanced so that items can be rearranged and items that aren't being shown do not take up space on the status bar. - Added the ability to show the local system time in the status bar. - When a selection is being made, the number of lines currently selected is shown in the status bar. Because only whole lines are counted, the selection must start at the beginning or end of a line. - Added a global option that allows the status bar to be shown in full-screen mode. - Added support for the rsa-sha2-256 and rsa-sha2-512 public-key algorithms (RFC 8332). - Added the ability to do a Google search on text selected in a session. - Added the ability to use wildcard characters "*" and "?" in the Session Manager filter box. - The multi-line paste option now allows the number of lines to be specified, providing additional control over when the Paste Confirmation dialog is shown. - Added an option that allows the Xterm escape sequence to copy to the clipboard (OSC 52). - SSH2: The host-key algorithms can now be specified and ordered in the Session Options dialog. - Windows: Added an administrative option that disallows a blank configuration passphrase. Changes: - SSH2: Removed support for several weak ciphers (Blowfish and RC4) and MACs (SHA1-96, MD5, and MD5-96). - In the multi-line paste confirmation dialog, the line-send delay value can be specified for the paste operation. - For TN3270 emulation, the default mapping of the Enter key was changed to ENTER/TRANSMIT (SHIFT+ENTER). - Added the ability to reorder sessions in the Auto Session list. - When connecting to a ProFTPD mod_sftp server, SFTP version 3 is used by default. - When IPv6 hostnames are displayed in tabs or the application title bar, the colons (":") are no longer replaced with underscores ("_"). - In the Manage Agent Keys dialog, the fingerprint is displayed as SHA-2. - For new keyword lists, the default Highlight style is "Color" instead of "Reverse video". - Added a session INI-file-only option "Alternate Screen Output Added To Scrollback" which allows alternate screen (e.g., tmux) output to be put in the scrollback buffer. - In the Global Options dialog, in the SSH Host Keys category, the Hostname and Port columns now sort logically instead of alphabetically. Bug Fixes: - If the "Display logon prompts in terminal window" option was enabled and the remote password contained a Unicode character, authentication may have failed to certain servers. - When attempting to connect to an ownCloud WebDav server, the initial connection and/or traversing the file system could have failed. - When connected to a remote host using the Raw protocol, data displayed on the screen could have been corrupted. - When connected to a Telnet server that did not respond to Kermit binary mode transition requests correctly, the Kermit transfer may have failed. - The display of certain Unicode characters (e.g., emojis) in the terminal could have caused other characters to appear as clipped. - Some global options did not take effect immediately after being set and saved in a script. - When using a mapped key configured to launch an application with an argument, the application failed to launch. - When using tab completion within an SFTP tab, filenames that contain spaces may not have autocompleted as expected. - When connected to certain remote systems and running applications (e.g., Aptitude) that support menu interaction using the mouse, clicking on a top level menu item may not have correctly displayed the dropdown menu. - When the title bar and/or tab naming options (/TITLEBAR and /N) were specified as part of a scripting connect call, neither the title bar or tab was named as expected. - When a log file was created in a location that contained a "." character somewhere in the path, the ".log" extension was not automatically appended to the filename. - If a session's log file path included the %F session folder replacement parameter and the "Start new log at midnight" logging option was enabled, the log file path used on the new day excluded the %F folder. - When the same session was connected multiple times simultaneously, the Session.LogFileName script function did not return the correct log filename for any of the secondary connections. - When editing multiple sessions simultaneously, and the state of the Logon Action "Hide" option was changed, only the first session was updated with the new value. - When the ImportArbitraryData example script was used to create thousands of sessions, and the session database already contained thousands of sessions, the session creation became very slow. - If a script was launched from a Button Bar button or keymap shortcut, and the script file could not be located, a misleading error was reported. - With certain network configurations, the TFTP server's listen address was incorrectly displayed on the status bar as a 169.254.*.* IP address, which is reserved for Automatic Private IP Addressing (APIPA). - Windows: If the internet connection was disconnected while downloading an available update via "Update Now...", the VanDykeUpdate application could have crashed. - Windows: When using CAPI to access a certificate located on a smart card, if the CAPI store contained multiple certificates, there could have be a delay before being prompted for the smart card pin. - Windows: If the Session Manager and Command Manager were docked in stacked layout, the size of the individual manager windows was not retained between instances of SecureCRT. - Windows: When the Command Window was displayed, the height of the window increased by one pixel each time SecureCRT was restarted. - Windows: If the Session Manager and Command Manager were docked within the same pane and configured to be auto-hidden, the expanded size of the managers could change when SecureCRT was restarted. - Windows: After upgrading from SecureCRT 6.5 or earlier, previously mapped keys that were configured to launch an application with arguments may have failed to work. - Windows: On high DPI monitors with a large scaling factor set, text displayed on the Keyboard Interactive authentication prompt could have been cut off. - Windows: When opening the "Script->Run..." dialog, the script name that was pre-populated in the filename field was partially scrolled out of view.