SecureCRT Changelog

What's new in SecureCRT 9.5.0 Build 3241

Jan 17, 2024

Bug Fix:
Windows: Closing an RDP session tab could have caused SecureCRT to hang.

New in SecureCRT 9.4.3 Build 3219 (Dec 19, 2023)

New in SecureCRT 9.4.2 Build 3191 (Nov 15, 2023)

New in SecureCRT 9.4.1 Build 3102 (Jul 18, 2023)

New in SecureCRT 9.3.2 Build 2978 (Feb 7, 2023)

New in SecureCRT 9.3.1 Build 2929 (Dec 6, 2022)

New in SecureCRT 9.3.0 Build 2905 (Nov 3, 2022)

New in SecureCRT 9.2.3 Build 2829 (Aug 2, 2022)

New in SecureCRT 9.3.0 Build 2803 Beta (Jun 29, 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 session in the Session Manager or Connect dialog.
Added the ability to duplicate local and remote port forwards.
Added the ability to correlate a PKCS#11 private key to an OpenSSH Trusted Certificate for public-key authentication.
Added the ability to configure the session font from the tab right-click menu.
Added a global INI-file-only option to disable tooltips for tabbed sessions.
Added the ability to use the algorithms [email protected] and
[email protected] as OpenSSH certificate types.
SSH2: Added support for using the x509v3-rsa2048-sha256 algorithm for authentication (RFC 6187).
Windows: Added support for using rsa-sha2-256 and rsa-sha2-512 public-key algorithms as raw SSH2 keys for CAPI certificates (RFC 8332).
Windows: Added support for using x509v3-ecdsa-sha2* algorithms from RFC 6187 for keys in the CAPI store and as raw SSH2 keys.
Windows: Added the ability to import RDP sessions using the Text Import wizard.
Windows: Added an administrative option that suppresses the prompt for a configuration passphrase the first time the application runs.
Windows: Added an administrative option that disables Expect/Send logon actions and logon scripts.
Windows: Added an administrative option for disabling non-secure file transfers.
Windows: Added the ability to pass command-line arguments to the shell for local shell sessions.
Windows: Added an icon for the "Keyword Highlighting" menu item, which can also be used when customizing the toolbar.
Windows: A suite of separate command-line utilities (formerly the VanDyke ClientPack) for securely automating file transfer, shell, and public-key administration tasks is included with SecureCRT.
Mac/Linux: The tarball installer includes a suite of separate command-line utilities (formerly the VanDyke ClientPack) for securely automating file transfer, shell, and public-key administration tasks.
Changes:
Improved speed of terminal output display when the host sends screen changes that do not cause scrolling.
Increased the character limit for keywords from 246 to 2048, which allows more complex regular expressions to be specified for keyword highlighting.
In the Edit Keyword dialog, the keyword text box is larger, which makes it easier to edit complex regular expressions for keyword highlighting.
The session option "Alternate Screen Output Added To Scrollback" can now be set in the Session Options dialog.
The "New Input" connection status indicator can be turned off.
The number of sessions that can be opened simultaneously before a warning is displayed can now be configured.
The session name is now included in the trace output.
SSH2: Trace output for the host key now includes the type and size.
SSH2: The View Host Key dialog now includes the type and size for the selected host key.
Windows: If there's a signature failure when attempting to load a Python DLL, a prompt is displayed, which allows the signature failure to be ignored once or always, or disable Python scripting.
Windows: When the Quick Connect dialog is displayed, initial focus is placed in the Protocol field when the global option "Use trackable insertion caret" is checked. Otherwise, initial focus is placed in the Hostname field.
Windows: Added the ability to set the "Close on disconnect" option for RDP sessions.
Windows: Added "Find" to the right-click menu for the scratchpad and script editor.
Windows: The default search direction is down when doing a find in a scratchpad or script editor.
Mac/Linux: When the Quick Connect dialog is displayed, initial focus is placed in the Hostname field.
Bug Fixes:
Under unknown conditions, a TFTP transfer from a Cisco device could have resulted in a crash.
If a script referenced a tab object for a tab that had been closed, SecureCRT could have crashed.
Modifying keyword highlighting settings could have caused SecureCRT to go unresponsive.
When connecting to multiple sessions sequentially, if the "Exit when last session is disconnected" option was enabled and the first session failed to connect, the application window closed, preventing subsequent sessions from connecting.
When resizing the window while there was text selected in the terminal view, the selection would not be cleared, resulting in the selection moving to a different block of text.
If keyword highlighting was disabled for a connected session, the highlighting was not cleared in the scrollback buffer.
When using the "Retain size and font" or "Scale the font" session resize options and all text in the view was selected, the selection may not have been cleared when the session window was resized.
When a YModem transfer over a serial connection between two paired COM ports successfully completed or was canceled, the Transfer menu items remained disabled.
Under certain scenarios, when using public-key authentication with agent forwarding enabled, keys were added to the remote agent.
If a session was disconnected while an alternate screen application (e.g., screen, mc) was running, the scrollback buffer was disabled if another session re-used the disconnected tab.
When setting the tab caption via a script, the window title was updated when the tab running the script did not have focus.
When a newly connected session re-used a disconnected tab, the "Add alternate screen output to scrollback" option state for the disconnected tab was used.
Windows: Under rare circumstances, when closing the application while an RDP session was connected, a crash could have occurred.
Windows: If the "Connect to multiple sessions sequentially" option was enabled and multiple RDP sessions attempted to connect at once, only one session connected.
Windows: If a Local Shell session was disconnected or closed while processing a large amount of scrolling data, SecureCRT could have become unresponsive.
Windows: When authenticating with a certificate from the personal CAPI store, if the "Use certificate as raw SSH2 key" option was enabled, the key was not correctly added to agent and a subsequent connection could have failed with an agent signature error.
Windows: When a large amount of data was scrolling within a local shell session, SecureCRT's memory and CPU usage could have been abnormally high.
Windows: When connecting to a server that used an X.509 certificate for the host key and 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 a Python 2 script was run from the Button Bar or Command Manager and the script was sent to multiple connected sessions, a dialog reporting a "Codec Registry" error may have been displayed.
Windows: When searching for text within a scratchpad or script editor session, the view did not scroll with the search.
Windows: When the "Single Instance" option was enabled, opening the "Connect..." or "Quick Connect..." options from the SecureCRT taskbar icon failed.
Windows: Multiple CAPI errors could have been reported when attempting to display a certificate fingerprint if the fingerprint for any certificate could not be obtained.
Windows: If the signature failed to verify for the protocol or Python DLLs, the file path displayed on the warning dialog may have been cut off.
Mac: When "Scale the font" resize method was configured for a session, the text displayed in the terminal view could have become unreadable with certain window sizes.
Mac: When the abbreviated SecureCRT menu bar was displayed (e.g., when the SecureCRT main window was closed to the dock), the "Update Now..." menu item failed to launch the update utility.
Mac: If a network connection was unavailable while checking for an update via "Update Now", the error displayed did not report a helpful message.
Mac/Linux: If the Command Manager was pinned or floating, sending a command to a session did not move focus to the terminal view.
Mac/Linux: When connected to a remote UNIX server using the SFTP tab, uploading a file that contained a colon character as part of the name would have been uploaded to the remote user's home directory instead of the current working directory.
VSFTP (Mac/Linux): When connected to a remote UNIX server, uploading a file that contained a colon character as part of the filename would have been uploaded to the remote user's home directory instead of the current working directory.

New in SecureCRT 9.2.2 Build 2794 (Jun 16, 2022)

New in SecureCRT 9.2.1 Build 2768 (May 12, 2022)

New in SecureCRT 9.2.0 Build 2693 Beta 2 (Feb 4, 2022)

New Feature:
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.

New in SecureCRT 9.2.0 Build 2659 Beta (Jan 7, 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.
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 MACalgorithm 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.
When RSA host keys are generated, there is now a minimum size of 1024.
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., GlobalSSH2 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.

New in SecureCRT 9.1.1 Build 2638 (Nov 23, 2021)

New in SecureCRT 9.1.0 Build 2571 Beta 5 (Aug 25, 2021)

New in SecureCRT 9.1.0 Build 2560 Beta 4 (Aug 16, 2021)

New in SecureCRT 9.1.0 Build 2544 Beta 3 (Jul 23, 2021)

New in SecureCRT 9.1.0 Build 2525 Beta 2 (Jun 30, 2021)

New in SecureCRT 9.1.0 Build 2507 Beta (Jun 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 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.

New in SecureCRT 9.0.2 Build 2496 (May 20, 2021)

New in SecureCRT 9.0.1 Build 2451 (Mar 19, 2021)

New in SecureCRT 9.0.0 Build 2430 (Feb 19, 2021)

New in SecureCRT 9.0.0 Build 2422 Beta 6 (Feb 10, 2021)

New in SecureCRT 9.0.0 Build 2411 Beta 5 (Jan 27, 2021)

New in SecureCRT 9.0.0 Build 2359 Beta (Nov 22, 2020)

New Features:
Windows: Added the ability to open files into a scratchpad tab or tile.
Mac: Added support for a Command Manager, which allows commands to be saved and organized within folders. Commands that can be saved include: sending strings, executing menu functions, running scripts, and running local applications. Also, button bars, including the buttons on the button bar, can be copied to the Command Manager and vice versa.
Mac: Added support for Python 3. An external Python 3.8 engine is required.
Linux: Added support for Ubuntu 20.04.
Linux: Added support for Python 3. On Ubuntu 20.04, the default Python 3.8 version is supported. On Ubuntu 18.04 and RHEL 8, the default Python 3.6 version is supported.
Changes:
The prompt for keys that are pre-loaded into agent now shows the filename associated with the key.
SSH2: When attempting an SSH2 connection, if KEX algorithm negotiation fails, SecureCRT offers to try again by enabling a supported algorithm.
The SHA-2 base64 hash of the public-key fingerprint is now displayed in the Public Key Properties and trace output.
Windows: RDP sessions now support smart cards.
Windows: RDP sessions no longer have to reconnect when the application window is resized.
Windows: The RDP option "Scaling" was changed to "Smart sizing" and a new "Scale factor" option was added.
Windows: Added the ability to disconnect and reconnect RDP sessions.
Windows: RDP sessions honor the global options "Exit when last session is disconnected" and "Show connection closed dialog".
Windows: If there are unsaved changes in a scratchpad tab or tile, when the tab or tile is closed, a prompt asking if the changes should be saved is displayed.
Mac: For new installations, the Kerberos key-exchange methods are off by default.
Bug Fixes:
If a very large file was specified as a public-key file, SecureCRT could crash when the file was loaded.
When attempting to connect to a server that did not reply to SSH_MSG_CHANNEL_REQUEST, SecureCRT could hang.
When connecting to a session that used public-key authentication, if the specified key did not exist on the remote system, the file browse dialog displayed to allow another public-key file to be selected had "::rawkey" text included in the file name field.
When using newer versions of Vim, a "2m" character sequence may have appeared on the screen due to an unsupported XTMODKEYS escape sequence.
Windows: When connecting to an RDP session, the scaling settings set on the local display were not honored.
Windows: If the "Reuse disconnected tab" global option was set and an RDP session was disconnected, attempting to connect another session silently failed.
Windows: When the session options were changed for a disconnected RDP session, the changes were not honored when the session was reconnected.
Windows: When connecting to an RDP session with the "Fit to panel" and "Scaling" display options enabled, if the window mode was set to tiled, the RDP view did not correctly scale to fit the window.
Windows: When an RDP session was connected and had focus, using ALT+TAB to switch to a different window, then back to SecureCRT did not put focus back into the RDP session.
Windows: If the "Show confirm disconnect dialog" option was enabled, disconnecting an RDP session did not prompt with the confirmation dialog.
Windows: When SecureCRT and SecureFX were installed as a combined installation (integrated) and an RDP session was created using the Quick Connect dialog, the transfer protocol was unexpectedly set to SFTP.
Windows: The scratchpad tab or tile was closed when "Close all not connected" was selected.
Windows: When pasting long lines of text into a Scratchpad session, the horizontal scrollbar may not have been displayed.
Windows: When a scratchpad session was opened in a maximized window in cascade mode, the scrollbars were not shown and hidden as expected.
Windows: When saving the scratchpad contents to a file using "Save As", the document filter type may have been unexpectedly set to Script.
Windows: If a scratchpad's name was changed and "Save As" was selected in the context menu, the name in the "Save As" dialog had an extra space at the end.
Windows: If scripting was administratively disabled, the Script menu was displayed the first time SecureCRT started. Note that any attempts to run a script still failed as expected.
Windows: When zooming in to increase the font size in the current terminal view, the font size may not have been the correct size after zooming back out the same number of times.
Windows: When the main window was maximized after closing the first opened tab, the terminal view of the remaining tabs was the incorrect size, causing the right side of the view to no longer scroll text and causing the lower portion of the view to appear blank.
Windows: If a "Send String" button contained a "," character sequence within the send string, after restarting the application, the text that appeared after the "," was stripped from the send string and used for the button label name.
Mac: When the number of available columns was less than the actual terminal view space and the application window was maximized, attempting to open another tabbed session or entering enough text in the second tabbed session to cause it to expand past the maximum number of columns could have resulted in a crash.
Mac/Linux: When the close tab keyboard shortcut (Command+W or Ctrl+F4) was sent to all tabs via the Command Window, SecureCRT could crash.
Mac: Attempting to authenticate using a YubiKey smart card with the "opensc-pkcs11.so" library specified as the PKCS#11 provider resulted in an error, because the library could not be loaded.
Mac: The application window was sometimes blank after regaining focus from another application, such as f.lux.
Mac: If the ZModem Upload List dialog was using the List view mode, which allows a folder to be expanded to display its contents, a file within an expanded folder could not be added to the upload list.
Mac: When using the built-in trackpad on a MacBook to drag a session to a different location in the Session Manager, auto- scroll and folder auto-expand did not work consistently.
Mac: After setting the font typeface for a session in the Session Options dialog, it was not possible to select a different font typeface.
Mac: When using certain fonts (e.g., Source Code Pro), not all of the font's typefaces could be selected.
Mac: Under certain circumstances, when an auto-hidden Session Manager was expanded, the Session Manager would briefly open, then immediately re-hide.
Mac: If the Session Manager was docked and in auto-hide mode, a "<>" text artifact appeared on the Session Manager tab when expanded.
Mac: If SecureCRT was open and the system appearance setting was changed from Dark Mode to Light Mode, the labels on the Button Bar buttons were too light.
Mac/Linux: If the Command Window "Send Characters Immediately" option was enabled, minimizing and restoring SecureCRT caused the option to be disabled.
Mac/Linux: When the close tab keyboard shortcut (Command+W or Ctrl+F4) was sent to all tabs via the Command Window, SecureCRT could crash.
Mac/Linux: When a public key that had a comment specified in the key data was added to the agent, the Manage Agent Keys dialog did not display the comment.
Mac/Linux: When enabling logging via the file menu, connecting to a session caused logging to be toggled off.
Mac/Linux: Text displayed on the Keyboard Interactive and View Host Key dialogs could not be selected or copied.
Linux: On systems with a display scaling factor set greater than 100%, the menu text and toolbar icons may not have scaled correctly.

New in SecureCRT 9.0.0 Build 2336 Beta (Oct 21, 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., domainusername), the resulting session duplicated the domain (i.e., domaindomainusername).
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 cascade tile mode could have resulted in a blank session window being displayed.
Windows: If the default.mnu file was specified as a custom .MNUfile, 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.

New in SecureCRT 9.0.0 Build 2315 Beta (Sep 25, 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.

New in SecureCRT 8.7.3 Build 2279 (Aug 11, 2020)

New in SecureCRT 8.7.2 Build 2214 (May 14, 2020)

New in SecureCRT 8.7.1 Build 2171 (Mar 17, 2020)

New feature:
- Windows: Added an administrative policy that disallows the TFTP
server from being run.
Changes:
- The performance of keyword highlighting has been improved to be
as fast as and in many cases, much faster, than version 8.5.
- SecureCRT now handles the Xterm "paste bracketing" escape
sequence so that indentation is correct when indented text is
pasted into an editor.
- Added an optional "hide output" parameter to the Session Object
Lock() method.
- SSH2: When doing public-key authentication, if there is no
corresponding private-key file without an extension and there
is a private-key file with a .ppk extension, it will be used.
- Mac/Linux: When ENTER is pressed on a folder in the Session
Manager, it is expanded or collapsed. Previously, all the
sessions in the folder were connected.
Vulnerability addressed:
TFTP: The TFTP server is off by default. However, when the TFTP server was running, SecureCRT was vulnerable to a directory traversal attack that allowed access to arbitrary files on the local system.
Bug fixes:
When running a version of the Midnight Commander file manager that supports extended coordinate mouse clicks, mouse operations from within SecureCRT did not work.
When multiple screens were created using the "screen" utility, the scrollback from one screen could end up in the scrollback for a different screen.
When multiple screens were created using the "screen" utility, the man page output went to the scrollback buffer
In the Manage Agent Keys dialog, the columns expanded every time the dialog opened, which eventually caused all column headers to disappear.
If two sessions were connected and then a session was sent to a new window, if the Hex view was opened, no data was displayed in the Hex view for the session.
The items "MENU_TOGGLE_KEYWORD_HIGHLIGHTING" and "MENU_CONNECT_LOCAL_SHELL" were not recognized when they were included in a custom .MNU file.
Windows: If folders were rearranged in the Command Manager, the folder order was not remembered when SecureCRT restarted.
Windows: If the Session Manager and Command Manager were unpinned (auto hide) and the Session Manager was pinned, the Command Manager became active.
Windows: Some of the arrow buttons in the Global and Session Options dialogs did not work correctly with screen readers, such as JAWS and NVDA.

New in SecureCRT 8.7.0 Build 2143 (Feb 11, 2020)

New in SecureCRT 8.7.0 Build 2134 Beta 4 (Jan 29, 2020)

Changes:
When SecureCRT is attempting to automatically reconnect a session after its connection has been lost, if the reconnect takes more than one attempt, the reconnecting message is updated in the terminal instead of being displayed again.
Windows: When the mouse hovers over a command in the Command Manager, a tooltip is shown in the Command Manager and in the status bar.
Bug fixes:
When multiple screens were created using the "screen" utility, the scrollback from one screen session could end up in the scrollback for a different screen session.
The "screen" utility's output was not cleared upon exit if the session used Xterm emulation and the "Enable 80/132 colum switching" option was on.
With two or more connected sessions, the button bar disappeared when switching between tabbed and tiled mode if the global button bar option was off and the session button bar option was on for one of the sessions.
When SecureCRT and SecureFX were integrated, if a connected session name contained Chinese characters, attempting to open that session in SecureFX by clicking the SecureFX button on SecureCRT's toolbar resulted in a "Session was not found in database" error.
If SecureFX was launched from SecureCRT with an unsaved Quick Connect session and then SecureFX was closed, the default session's hostname was set to the Quick Connect session's hostname.
Windows: When a session was opened in a new window, the Command Manager was displayed briefly if it was docked and unpinned (auto-hide).
Mac: If there were a small number of saved sessions, SecureCRTcould hang when a session or folder was renamed or moved.
Mac: If the Session Manager was moved to a different monitor, when SecureCRT restarted, the Session Manager was displayed on the same monitor as SecureCRT.
Mac: If the Session Manager was moved, when SecureCRT restarted, the Session Manager was positioned at its location prior to being moved.
Mac: If password authentication failed when attempting to connect to a session, the "Skip" button was the default button in the Password Authentication Failed dialog.
Linux: On the Confirm Multi-line Paste dialog, checking the "Do not show this dialog again" option changed the default button from Paste to Cancel.
Linux: The Index, Glossary, and Search help tabs did not work correctly.

New in SecureCRT 8.7.0 Build 2109 Beta 3 (Jan 11, 2020)

New in SecureCRT 8.7.0 Build 2079 Beta (Nov 21, 2019)

New features:
Windows: Added support for a Command Manager, which allows commands to be saved and organized within folders. Commands that can be saved include: sending strings, executing menu functions, running scripts, and running local applications. Also, button bars, including the buttons on the button bar, can be copied to the Command Manager and vice versa.
Windows: Added support for opening a local shell (CMD or PowerShell) session within SecureCRT. Due to Microsoft's Pseudo Console API availability, support for this feature is limited to Windows 10 build 1809 and Windows Server 2019 or later.
Mac: Added support for Dark Mode on macOS 10.14 and later.
Keyword highlighting supports the ability to match phrases and substrings and works with literal strings and regular expressions.
Windows: Improved the GUI for keyword highlighting configuration.
Linux: Added keyword highlighting support for regular expressions.
The Session Manager and Connect Dialog session filter fields now have the ability to filter sessions based on the top-level folder the sessions reside in. When filtering, the folder name must be followed by the forward slash character in order to list the sessions within that folder.
Mac/Linux: Session windows can now be tiled in both horizontal and vertical layouts.
The "Hex view buffer" can be configured to have up to 32,000 lines.
The "Hex View" now shows hex data independently for each connected session.
A selection made on the hexadecimal pane or the ASCII pane is reflected in the other pane and the ASCII pane can also be hidden.
In the "Hex View", SHIFT+<click> can be used to extend an existing selection, similar to behavior supported in the terminal window.
When a session is locked, there's an option to hide all output, which adds an extra layer of security.
Added a global option "Allow overwrite of existing files" that allows TFTP transfers to overwrite files that already exist.
The built-in TFTP server now honors the block size set by the TFTP client for valid values as specified in RFC 2347.
The TFTP server listen address and port are now displayed in the status bar when the server is running.
Added support for TVI925 and TVI910 emulations.
SSH2: Added support for the diffie-hellman-group14-sha256, diffie-hellman-group16-sha512, and diffie-hellman-group18-sha512 key-exchange algorithms.
SSH2: Added support for x509v3-ecdsa-sha2 algorithms per RFC 6187 for PKCS #11.
The audio bell can be configured to play a sound file.
Added a global option that allows the Command window option "Send Characters Immediately" to be enabled by default.
Added a "Log Screen" INI-file-only session option that allows all data displayed in the terminal to be logged at the time it appears on screen.
Added the ability to map keys and buttons to the menu functions "Paste as Quotation" and "Hex View" (toggle).
Added scripting support for retrieving and setting global configuration options.
Added the ability to set window and tab captions independently in the Session Options dialog and from a script.
Added the ability to export and import just the button bars.
Added a command-line flag "/KEX" that allows the key-exchange algorithm(s) to be specified on the command line.
Windows: Added a new firewall type "Proxy command" which allows a local proxy command to be run when connecting to a remote server.
Windows: Added the ability to set commands to the menu functions "Paste as Quotation" and "Hex View" (toggle) in the Command Manager.
Mac: Added the ability to switch tabs (using CTRL+TAB and SHIFT+CTRL+TAB) when focus is in the Command Window. This functionality was already supported on Windows and Linux platforms.
Linux: Support for Ubuntu 19.04 has been added.
Changes:
Mac: macOS installers are now notarized by Apple. This tells Gatekeeper on the system that the software has been scanned by Apple for malicious software and is trusted.
When entering full-screen mode, a hint describing the process to exit full-screen mode is momentarily displayed.
The Find dialog now has a "Wrap around" option, which provides a way to control what happens when the end of the buffer is reached.
If a firewall name is changed, any sessions using that firewall are updated with the new firewall name.
If a session is renamed or moved, any sessions using that session as a dependent session firewall are updated with the new session name or location.
When generating a new RSA key, the default size is now 3072 bits.
The flow control setting "XON/XOFF" is on by default for Serial sessions. This only affects new installations.
The name of the active session is shown in the "Hex View" title bar.
Moved the "Hex View" menu item from the File menu to the View menu.
The global option "Command window history" was moved from the Terminal/Appearance category to the Terminal/Advanced category.
TFTP settings are now platform specific.
The TFTP upload, download, and log file paths can use a templated path, which gets modified to an appropriate path on each platform.
Added the ability to wait for milliseconds in the script functions WaitForCursor, WaitForKey, WaitForString, and WaitForStrings.
SecureCRT honors ports and titles specified in URLs.
SSH2: If a session's username is empty and the saved password is empty or incorrect, the username is now saved when it is entered in the Enter Secure Shell Password dialog and the "Save password" option is checked. Previously, the username could be entered in the dialog, but was not saved to the session.
The username specified for a session can be changed and saved via the Failed Authentication dialog. Previously, the username could be changed, but that change was not saved to the session.
With smart-card authentication, the presence of the private key is now verified before attempting to use the corresponding public key.
When deleting a key from agent, a confirmation dialog is displayed before the key is deleted.
SecureCRT now logs when the SSH_MSG_USERAUTH_PK_OK response is received from the server during public-key authentication.
The product version is now shown in the expired license dialog.
Windows: The VanDyke Update utility now reports the actual error text, rather than just an error number, when checking for updates fails.
Bug fixes:
When running a script that set the session configuration emulation option to an invalid value, SecureCRT crashed.
When specifying a very long string (1000+ characters) as a Button Bar or Button name, unexpected behavior could occur, including display issues, the inability to delete the Button Bar/Button, and a potential crash. SecureCRT now limits the Button Bar and Button names to 100 characters.
When running a script that opened and closed multiple sessions, including an SFTP tab, SecureCRT could potentially crash.
SecureCRT hung after closing a session that was running a logon script.
SecureCRT could become unresponsive when a lot of data was being output to a session that was using keyword highlighting.
If a string greater than 5000 characters in length was entered in certain fields (Connect Bar, Search Filter, etc.), SecureCRT could freeze.
When using the personal data configuration option, it was possible to get into a situation where both the main configuration folder and the personal data folder were pointing at the same location, which could have caused the personal data (e.g., usernames, passwords, etc.) to be lost.
If the "Store personal data separately" option was enabled, the "Use login script" session option was not included in the options stored in the personal data folder. The login script data itself was already stored in the separate personal folder.
Deleting a keyword list named "." or ".." could have resulted in all configuration data being deleted. Keyword list names now follow the same naming rules applied to session names.
When an invalid or expired license was encountered at startup, SecureCRT failed to look in other locations for a valid license.
When connected to a Telnet server that did not respond to ZModem binary mode transition requests correctly, the ZModem transfer could fail.
Connecting to a newly created or ad-hoc TAPI session without first pressing the modem "Configure..." button could have resulted in a "Failed to run modem configuration" error.
If the session tab name was set by an escape sequence sent by the remote server, sending that tab to a new window caused the tab name to revert to the actual session name.
Dragging a session tab to another window with an already connected session may have resulted in the wrong terminal size for the moved session.
If the "Scale the font" terminal resize session option was set and the window was maximized, the last row in the terminal could be cut off.
When backspacing over characters in the terminal, the overall line length was not reduced by the same amount, resulting in unexpected whitespace at the end of the line.
If a session was maximized and the prompt was on the last line, zooming caused the last line to go off the screen.
If a session was zoomed in or out many times, the session could get in a state where some of the rows were not visible and scrolling did not work.
When multiple sessions were opened in tabs with at least one of the sessions zoomed, resetting the zoomed session could result in an incorrect terminal or window size.
When opening the Global Options dialog, the SecureCRT URL handler open command was being reset to the default URL handler.
When the global "Save window state for each session" option was enabled, the window position and size may have been incorrect for newly created sessions.
If a connected session with the "Disable Resize" option set was closed, the SecureCRT window could not be resized.
When the "Minimize Drawing" session option was enabled, certain data patterns could cause the screen scrolling to appear in a strange manner.
When connecting to a session that had the "Log Screen" option enabled and the connection was re-using a disconnected tab, logging did not start correctly.
If logging was started before connecting to a session, the custom log data "Upon Connect" field value was not written to the log file.
Raw protocol sessions did not honor the "Local echo" session option.
When connected to a device using the Raw protocol, characters were not sent immediately as expected.
When the "Show Session Manager or Connect dialog on startup" option was enabled and the Session Manager was in an auto-hidden state, at startup the Session Manager remained hidden and was not given focus.
When the Session Manager or Connect dialog tree was arranged manually, folders may not have been displayed in the expected order.
Under certain circumstances, the Session Manager did not open when using the ALT+N keyboard shortcut.
If the Find dialog's last opened position was on a monitor that was no longer connected, it was not visible on the current monitor when it was reopened.
When saving an ad-hoc session, the session's color scheme was not saved correctly.
When attempting to save an ad-hoc connection using the SessionConfig scripting object's Save method, the hostname and user credentials were not always saved to the session.
When using the WaitForStrings() scripting function, the specified timeout was not always honored.
When configuring a dependent session as a firewall (jump host), a session that was invalid for the current session could have been selected by double clicking the invalid session.
When SecureCRT and SecureFX were installed as a combined installation (integrated) and a configuration import or export operation was performed from SecureFX, SecureCRT's button bar configuration was not included in the import/export.
When using the Session Manager, changes made to existing sessions by a configuration import were not shown until SecureCRT restarted.
Immediately after importing a configuration that included a 3-year license, the About dialog displayed an incorrect license expiration date. The correct expiration date was displayed when SecureCRT was restarted.
When importing a configuration that contained Button Bar settings created using an older version of SecureCRT (8.3 or earlier), the Button Bar settings were not imported.
When a Button Bar button was configured to launch a script located under the configuration folder, the script file path was not stored using the cross-platform templated path (VDS_CONFIG_PATH).
Windows: When using both the left and right mouse buttons to simulate a middle button click, and the "Paste on middle button" option was enabled, the paste operation did not succeed.
Windows: SecureCRT could crash when RDP was used to connect to a remote machine and SecureCRT was launched on the remote machine and the RDP connection was closed and then later reestablished.
Windows: Under rare circumstances, SecureCRT could crash at startup.
Windows: If a number key on the numpad was previously mapped, when editing that keymap, SecureCRT could crash.
Windows: When the default session protocol was set to Telnet or RLogin, opening an "SSH://<host>" URL failed.
Windows: When the "Display logon prompts in terminal window" option was enabled, the DUO multi-factor authentication prompt was not displayed correctly.
Windows: If SecureCRT was maximized or full screen and the font was zoomed in using CTRL+ or the mouse wheel, attempting to zoom out using CTRL- or the mouse wheel did not work.
Windows: If the SecureCRT terminal view was zoomed after clicking in the terminal, text was unexpectedly selected.
Windows: On high DPI monitors that had a scale factor applied, the font size displayed in the Hex View did not match the size displayed in the font chooser dialog.
Windows: On some Windows operating systems, starting SecureCRT could cause all desktop icons to refresh.
Windows: When the window transparency option was enabled, the SecureCRT window flashed anytime a new connection was made.
Windows: In a multiple-monitor environment with a maximized SecureCRT window, using the SHIFT+Win+Arrow keyboard shortcut to move SecureCRT to another monitor could fail to move the window.
Windows: When the character encoding was set to "None", the trace output may have displayed many duplicated lines.
Windows: When the "Allow Proportional Fonts" option was enabled, proportional fonts appeared smaller in the terminal than what was shown in the font chooser dialog.
Mac/Linux: SecureCRT crashed when a file was dragged and dropped on the tab bar, status bar, or button bar.
Mac/Linux: When clicking the "View Host Key" button on the "New Host Key" dialog, the host key was rejected instead of being displayed.
Mac/Linux: Connecting to a server that was configured with a 4096-bit DSA host key could result in an unsupported bit size error.
Mac/Linux: When multiple SecureCRT windows were open and global options were modified, the focus could unexpectedly change to a different window after the Global Options dialog was closed.
Mac/Linux: When changing the scrollback buffer size for a connected session, the updated size did not take effect until the session was reconnected.
Mac/Linux: Under certain circumstances, the expanded/collapsed state of the folders in the Session Manager could reset to the state they were in at application startup.
Mac: If SecureCRT was attempting to report a previous crash, the Crash Reporter itself could have crashed if it was closed via the dock icon.
Mac: When the VoiceOver accessibility option was enabled on the system, SecureCRT could crash when certain dialogs were opened.
Mac: On macOS 10.15, if the session log file prompt was displayed, all menu items were disabled after the prompt was dismissed.
Mac: On macOS 10.14, certain drag and drop operations (e.g., dragging a session within the Session Manager) could have resulted in a system accessibility dialog requesting additional access be granted to the application.
Mac: Opening a URL from the terminal using the COMMAND+<click> combination failed.
Mac: When running SecureCRT a macOS 10.13, the window could have been painted incorrectly when switching between SecureCRT and other applications.
Mac: When SecureCRT was displayed on a secondary monitor, double clicking the title bar to maximize it caused it to be maximized on the primary monitor.
Mac: Dragging a session or folder into another folder caused that session or folder to be hidden from view. The moved session or folder was displayed correctly after SecureCRT restarted.
Mac: If there were multiple lines in the Command Window, pressing the HOME or END keys moved the cursor to the beginning/end of the text block instead of the beginning/end of the current line.
Mac: Under certain circumstances, if the SecureCRT main window was minimized while an auto-hidden Session Manager was displayed, the Session Manager did not minimize with the main window and remained visible on the screen.
Mac: When opening certain dialogs (e.g., Session Options), the dialog may have opened in the upper left corner of the monitor, instead of centered over the main window.
Mac: When the "Save expanded folder state in connect dialog" global option was set, under certain circumstances, the expanded state was not saved correctly.
Mac: The global option "Command window history" only allowed a four-digit number to be entered, even though the maximum supported value is 32000.
Linux: On Ubuntu 19.04, when running SecureCRT on certain older hardware, the application could crash at startup.

New in SecureCRT 8.5.4 Build 1942 (May 30, 2019)

New in SecureCRT 8.5.3 Build 1867 (Feb 12, 2019)

New in SecureCRT 8.5.2 (Nov 16, 2018)

New in SecureCRT 8.5.1 (Sep 28, 2018)

New in SecureCRT 8.5 (Aug 29, 2018)

New in SecureCRT 8.5 Beta 4 (Aug 10, 2018)

New in SecureCRT 8.3.4 (Jul 13, 2018)

New in SecureCRT 8.5.0 Build 1689 Beta 1 (Jun 28, 2018)

NEW FEATURES:
Added a Button Bar Manager, which allows button bars to be added, duplicated, edited, deleted, and arranged manually or alphabetically.
Added a Button Manager, which allows buttons on a button bar to be rearranged, edited, added, deleted, copied, and pasted.
Added the ability to rename button bars.
Button bars can be duplicated from the button bar context menu and in the Button Bar Manager.
Added the ability to map a button or key to a button bar, making it easier to switch between different button bars.
The text in the multi-line paste confirmation dialog can be edited before it gets pasted into a session.
The multi-line paste confirmation dialog can be resized.
Added the ability to save sessions that were created using Quick Connect, the Connect bar, or the command line.
Added a new Script status indicator so that tabbed and tiled sessions can indicate that a script is running.
Added a global option to disable all printing.
Added a global option that allows the Command window to be configured to send commands to all sessions, visible sessions, or the active session by default.
Added the ability to make the width of session tabs a fixed number of pixels.
Added support for the SHA2-512-EtM and SHA2-256-EtM MACs. ssh-add can be used to add keys from a remote Linux, Unix, or Mac system to SecureCRT's agent using agent forwarding.
Added the ability to specify the quote character(s) to be used for the "Paste as Quotation" operation.
Added a global option to prevent numbers from being appended to tabbed or session names when the same session is connected more than once.
Added "Reset Name" to the tab/tile context menu, which resets the tabbed or tiled session name back to the session's name or title specified in the Session Options dialog.
Added the ability to toggle keyword highlighting from the Options menu.
When a session is copied in the Session Manager or Connect dialog, the session's hostname is put in the clipboard so that it can be pasted into a session or other applications. The session can still be pasted into the Session Manager or Connect dialog.
Added a global option to disable ALT+<number> tab switching.
Added a global option for triple clicking to include the EOL character in the selection.
Sorting on columns is supported in all list controls that have columns.
Added a session INI-file-only option "Keyboard Interactive Prompt" that allows the expected prompt for keyboard-interactive authentication to be specified.
Added a command-line flag /KEYBOARDINTERACTIVEPROMPT that allows the keyboard interactive prompt to be specified for SSH2 sessions.
Added a global INI-file-only option "TFTP Resend Timeout" that allows the resend timeout for the TFTP server to be configured.
CHANGES:
Because of an update to a cryptographic library used by SecureCRT, newly generated DSA keys are now restricted to 1024 bits.
In the Public Key Properties dialog, the "Use identity orcertificate file" field can be left blank.
The Full Reset and Soft Terminal Reset escape sequences are now honored with Linux, VShell, VT220, VT320, and Xterm emulations.
The DECSUSR escape sequences to change the cursor style are now honored in Xterm emulation.
Preceding and trailing whitespace is removed from hosts entered in the Connect bar.
Made it easier to specify xterm-256color emulation in the Session Options dialog.
Added base color support for TN3270 emulation.
If the global option to paste on press of middle mouse button is set, the middle mouse button can be used to paste into the Command window.
An optional confirmation dialog is displayed on the "Paste as Quotation" operation.
If the session option "Forward X11 packets" is set and no X server is running on the local machine, a warning dialog is no longer displayed.
If the session options "Automate logon" and "Send initial carriage return" are set and no Send strings are specified, the initial carriage return is sent when the session connects.
The session option "Disable initial SFTP extensions" can now be configured in the GUI.
The local and remote port forwarding fields in the Session Options dialog have been made taller so that more configured port forwards are visible.
Added the ability to specify the terminal type on the command line using the flag /TERMINAL_TYPE.
When the options /COLOR_SCHEME and /T are used on the command line, the color scheme is only applied to the session specified by /T.
SSH1/SSH2: If the option "Do not request a shell" is set, a message to that effect is displayed in the session.
Windows: For the VS2018 Dark theme, the active tab's color was lightened so that it would stand out more.
Windows: The close button for the "Native" display theme is now a plain "X".
BUG FIXES:
If two instances of SecureCRT were running and the Global Options dialog was displayed in one instance and the Session Options dialog was displayed in the other, if changes were made in the Global Options dialog and saved, SecureCRT crashed when attempting to select a different category in the Session Options dialog.
In the Session Manager or Connect dialog, if a folder was renamed to have a name that was too long for the local system, the sessions contained in the folder were deleted.
SecureCRT hung when running a Python script that called crt.Screen.Send("00).
SecureCRT failed to authenticate with remote systems, such as the Balabit PPM SSH proxy server, that requested the same authentication method more than once during authentication.
If SecureFX was also installed and the terminal protocol in the default session was set to None, SecureCRT could not be launched.
When the script recorder was used to generate a Python script, escape characters [chr(92)] were not included in the script.
When exporting settings, scripts that were used by buttons were not exported.
If keyword highlighting was turned on through a script, the terminal window was not updated to highlight the keywords.
The multi-line paste dialog did not display the text correctly if the session was using the vt100 font and the configuration data was from a version of SecureCRT between 6.0 and 6.2.
Characters in the upper range of Unicode code points, such as emojis and certain Asian characters were rendered incorrectly or as unknown characters in the terminal area.
Some double-wide Unicode characters could not be used in keyword highlighting.
If SecureCRT was maximized and the Session Manager was made wider, when SecureCRT restarted, the Session Manager's size change was lost.
Windows: After SecureCRT had been running for a while, switching tabs could become very slow.
Windows: If the combined SecureCRT and SecureFX installer had previously been installed and then a newer standalone version of SecureCRT was installed, SecureCRT's menu bar was blank.
Windows: On a 4K monitor, if a session's resize option was set to "Synchronize view to size" and the view was zoomed several times, the prompt could end up off the screen and/or lines could be cut off.
Windows: If the EOL character for the text in the clipboard was not CRLF, line breaks were not displayed correctly in the multi-line paste confirmation dialog.
Windows: When the New Session wizard was used to create a Serial session, an invalid baud rate could be specified.
Windows: If the toolbar was customized to have a button for starting and stopping the TFTP server and the TFTP server failed to start, the button said "Stop TFTP Server."
Windows: In the Windows 10 Creators Update, the Session Manager and Connect dialog could be unresponsive for several seconds when they were displayed.
Windows: In the Windows 10 Creators Update, the Connect dialog could take several seconds to draw the toolbar.

New in SecureCRT 8.3.3 Build 1464 (May 3, 2018)

New in SecureCRT 8.3.2 Build 1584 (Feb 8, 2018)

New in SecureCRT 8.3.1 Build 1537 (Dec 7, 2017)

New in SecureCRT 8.3.0 Build 1509 Beta 4 (Nov 2, 2017)

New in SecureCRT 8.3.0 Build 1491 Beta 3 (Oct 12, 2017)

New in SecureCRT 8.3.0 Build 1483 Beta 2 (Oct 4, 2017)

New in SecureCRT 8.3.0 Build 1474 Beta 1 (Sep 22, 2017)

New features:
Added several new built-in color schemes, including the Solarized color schemes. There is a variety of light and dark color schemes, all of which have coordinated background, foreground, and ANSI color combinations.
Multiple global ANSI color palettes can be defined and a specific color palette can be specified for a color scheme.
Added autocomplete to the Connect bar in the toolbar, which makes finding and connecting to saved sessions easier.
When the SecureCRT window is resized, the text in the terminal area is rewrapped if the "On resize" option is set to "Synchronize view to size".
A paste confirmation dialog option allows you to preview the contents of the paste buffer before pasting multiple lines of text into a session.
Multiple sessions can be dragged and dropped or copied and pasted in the Session Manager and Connect dialog.
SSH2: Added support for the ChaCha20/Poly1305 cipher.
SSH2: Added support for the AES-GCM cipher.
SSH2: Added support for the UMAC-128 MAC algorithm.
SSH2: Added the ability to use OpenSSH certificates for authenticating SSH2 sessions.
SSH2: If a session cannot be cloned or connected using SFTP on the existing SSH connection, SecureCRT will create a new connection.
Added a tab context menu item that closes all sessions in the
current tab group.
Added the ability to script session locking from the Session object.
Added a substitution parameter %F that can be used to specify the session's subfolder in a log filename.
Added a command-line option /FORWARDX11PACKETS to enable X11 forwarding.
Platform-specific configuration settings such as font and window position are now stored separately for each platform which is helpful if settings are saved on a network drive and used on different platforms.
Windows: Added an Administrative Policy option to disconnect sessions authenticated using CAPI/PKCS#11 when the corresponding smart card is removed.
Windows: Added the ability to hide the title bar for the Command window.
Changes:
Up to 20 sessions can be included on the recent session list.
Middle clicking on the title bar of a tiled session closes the session.
Added a global INI-file-only option to specify the script path.
The session level ANSI colors were removed since multiple global ANSI color palettes can be created.
SSH2: Modified the default authentication order to be PublicKey, Keyboard Interactive, Password, and GSSAPI. This only affects new installations.
The session option "Minimize drawing (faster)" is now on by default. This change only affects new installations.
The default session filter delay has been changed from 500 milliseconds to 250 milliseconds. This only affects new installations.
For SSH1 and SSH2 sessions, if the session option "Backspace sends Delete" is set, the opcode for Erase is set to ^? (delete), which results in stty -a reporting erase = ^? and tells the terminal that the erase character is Delete.
The keyboard accelerators ALT+1 through ALT+0 only operate on the current tab group.
Added support for the %P logging substitution for Serial sessions.
If the global option "Show Session Manager or Connect dialog on startup" is set, the Session Manager is displayed when SecureCRT starts. Previously, only the Connect dialog honored this option.
If SecureCRT is launched using the -F command-line parameter or is on a USB drive, the actual configuration path being used is shown in the Global Options dialog.
When saving a recorded script, if the file extension is blank, the appropriate .vbs or .py extension is used.
SSH2: If a session is using public-key authentication and the key file has not specified, the user is no longer prompted to specify the file.
SSH2: When importing an SSH2 host key, if it's possible to extract the hostname, IP address, and port from the filename, those values will be used as the default values. Otherwise, the default value for port will be set to 22 and the other values will be left blank.
SSH2: When being prompted to accept an SSH2 host key, the fingerprints are now shown in a separate dialog.
SSH2: Pressing the SHIFT key in the New Host Key dialog allows a host key to be saved once.
In the View Host Key dialog, all the fingerprints can be selected at once.
In the View Host Key dialog, SHA-2 fingerprints are displayed in base64 in addition to hexadecimal.
SSH2: In the dialogs that prompt to accept the host key, the
SHA-2 fingerprint is also displayed in base64.
SSH2: The trace output shows the SHA-2 host key fingerprint as base64 in addition to hexadecimal.
The username used for authentication is now logged in the trace output.
Trace output now includes printer initialization information.
The Send String field in the Map Button and Map Selected Key dialogs was made larger vertically and horizontally.
The X11 forwarding display option can now be configured in the Session Options dialog.
Bug fixes:
SecureCRT crashed when the system time went to midnight if the logging option "Start new log at midnight" was set and the log file name contained the substitution parameter %D.
Windows: SecureCRT crashed if a session was being configured and the protocol was changed while a TAPI system prompt was displayed.
A session could become slow or non-responsive if another session was receiving and logging a lot of output.
Filtered searches in the Session Manager and Connect dialog could be very slow when the session database contained thousands of sessions.
Using Quick Connect to connect to a Serial session did not work.
TFTP transfers failed when an IPv6 address was used for the remote system (macOS Sierra uses IPv6 addresses by default.)
When an illegal character, such as a colon, was used in a log file name, logging failed silently. Illegal characters can no longer be used in a log file name.
In the New Session wizard and the Quick Connect dialog, once a session was selected as the Firewall, "Select Session..." was no
longer in the Firewall dropdown list.
If a session was configured to start logging upon connect and "Log Session" or "Raw Log Session" was selected from the File menu before connecting to that session, logging was turned off.
If a button bar name was empty or contained a quote character ("), the button bar was not available after SecureCRT restarted. Button bar names can no longer be empty or contain quote characters.
Long button bar names were not completely visible in the button bar dropdown list.
If a value larger than 32,000 was entered as the maximum number of columns in the Global Options dialog, no error was reported and a smaller value was used.
Attempting to modify protocol-specific options after changing the protocol for a SessionConfig object in a script did not work.
If the protocol options /SSH2, /SSH1, or /TELNET were specified on the command line or in the Connect bar without specifying a host, an error was reported.
Windows: If a session tab had focus or the mouse hovered over a session tab, pressing ALT+<spacebar> did not bring up the Windows system menu.
Windows: If the Connect bar was showing a dropdown list, pressing ALT+Q displayed the Quick Connect dialog, but did not put focus there.
Windows: Some printer setting changes made from the Print Setup dialog were not saved.
Windows: On high-DPI monitors, the EULA dialog in the installer did not display correctly.

New in SecureCRT 8.1.3 Build 1382 (May 23, 2017)

New in SecureCRT 8.1.2 Build 1362 (Apr 28, 2017)

New in SecureCRT 8.1.1 Build 1319 (Feb 28, 2017)

New in SecureCRT 8.1 Beta 5 (Jan 18, 2017)

New in SecureCRT 8.1 Beta 4 (Dec 20, 2016)

New in SecureCRT 8.0.4 Build 1252 (Dec 6, 2016)

New in SecureCRT 8.1 Beta 3 (Dec 2, 2016)

New in SecureCRT 8.1 Beta 2 (Nov 10, 2016)

New in SecureCRT 8.1 Beta (Oct 28, 2016)

New in SecureCRT 8.0.3 Build 1183 (Sep 9, 2016)

New in SecureCRT 8.0.2 Build 1118 (Jun 24, 2016)

New in SecureCRT 8.0.1 Build 1082 (Apr 26, 2016)

New in SecureCRT 8.0.0 Build 1063 (Mar 31, 2016)

New in SecureCRT 8.0.0 Build 1055 Beta 5 (Mar 22, 2016)

New in SecureCRT 8.0.0 Build 1045 Beta 4 (Mar 21, 2016)

New in SecureCRT 8.0.0 Build 1028 Beta 3 (Feb 25, 2016)

New in SecureCRT 7.3.7 Build 1034 (Feb 25, 2016)

New in SecureCRT 8.0.0 Build 1020 Beta 2 (Feb 9, 2016)

New in SecureCRT 8.0.0 Build 1011 Beta 1 (Jan 29, 2016)

New features:
Windows: Added support for tab groups, which provides another option for organizing connected sessions and doing side-by-side comparisons of session output.
Windows: The user interface has new themes and new toolbar icons.
Windows: Buttons on the button bar can be arranged by dragging and dropping when the ALT key is pressed.
Windows: Added support for high-DPI monitors.
Added support for TN3270 emulation.
Added support for the VT320 status line.
Added a "Send Characters Immediately" mode to the Command window, which makes it possible to do the following in one or multiple sessions: stop commands using CTRL+C, edit files using an editor such as vi, send escape sequences, and do tab completion.
Added the ability to start the TFTP server when SecureCRT starts, when any session connects, and manually.
Added the ability to use and generate ECDSA (RFC 5656) and Ed25519 keys.
Added the ability to generate keys in the new OpenSSH format.
SSH2: PuTTY PPK keys can be used for public-key authentication.
SSH2: On Windows, enhanced public-key authentication to allow a public key to be specified from the CAPI or PKCS #11 store.
SSH2: On Windows, public keys can be exported in OpenSSH format and can be exported from PKCS #11.
SSH2: On Windows, certificates can be used as a raw key for public-key authentication.
SSH2: On Windows, added support for X.509 authentication using the x509v3-ssh-rsa and x509v3-ssh-dss algorithms as specified in RFC 6187.
SSH2: On Windows, X.509 v3 keys can be added to the SSH agent.
SSH2: Added an SSH INI-file-only option called "Automatically
Accept Host Keys", which allows host keys to be accepted automatically. Note: Enabling this option is not considered a security best practice.
SSH2: Added a session INI-file-only option "Ident String" that allows the SecureCRT identity string to be specified.
Added a "Close All Not Connected" item to the tabbed/tiled session right-click menu, which makes it easy to close all sessions that are not currently connected.
Added a menu item to the Zoom pull-right menu in the View menu that allows a session to be restored to its original size if it has been zoomed.
Added an option for disabling session zooming with keyboard shortcuts to the Global Options dialog.
Added support for Xterm OSC escape sequences to change background and foreground colors.
In the Session Manager and Connect dialog, it's now possible to connect a session or sessions in a new window without changing the option that specifies whether or not sessions should be opened in a tab.
The connection status icons were updated.
Windows: Updated the icons in the Session Manager and Connect dialog.
Windows: Added the ability to make SecureCRT the default application for the URI "ssh://".
Changes:
By default, SecureCRT now listens for port forward requests only on 127.0.0.1.
Improved the drawing performance of keyword highlighting.
Quick Connect sessions that are saved are put in the current folder in the Session Manager.
Added a keyboard shortcut for the "Reconnect All" menu item.
The ability to use a session as a firewall has been added to the
Quick Connect dialog and the Session wizard.
The escape sequence "CSI ?3l" is ignored when the SecureCRT window is maximized or full screen.
Added the ability to map a key or button to display the Global or
Session Options dialogs.
In the Session Manager, when a folder or multiple sessions are selected, selecting the new menu item "Connect in Tabs in New
Window" opens the selected sessions in tabs in a new SecureCRT window.
Changed the SSL GUI protocol name to "Telnet/TLS" to reflect that TLS is supported.
Added "Contact Support" to the Help menu.
SSH2: If host key authentication fails with the ssh-dss algorithm, the ssh-rsa algorithm is preferred on subsequent attempts to reconnect the session.
SSH2: It's now possible to specify the minimum group exchange prime size in the Session Options dialog.
SSH2: SecureCRT can now connect to Cisco devices that send the incorrect identity string "SSH-2.99-Cisco-1.25".
SSH2: The "diffie-hellman" key exchange algorithm is off for the default session. This change only affects new installations.
SSH2: SHA-1 and SHA-2 fingerprints are displayed for public keys in addition to MD5.
SSH2: In all places where the host key fingerprint is displayed, the SHA-2 fingerprint is also displayed.
Windows: Updated the included Python library to version 2.7.
Windows: The background color for the selected theme is used as the background for the terminal area when SecureCRT starts and no sessions are connected.
Windows: If there is nothing in the clipboard that can be pasted into SecureCRT, all paste operations are either disabled or ignored, which eliminates the "General clipboard failure" error message.
Windows: If the administrative policy "Enable Check For Updates" is set to false, "Update Now" is not allowed.
Windows: Only PNG files can be used as images in custom menu MNU) files.
Bug fixes:
Attempting to delete a session without a name caused every session in the session database to be deleted.
If SecureCRT had insufficient permissions to access a configuration folder located on OneDrive, SecureCRT crashed.
SecureCRT could become unresponsive when settings were being imported or exported, especially when the configuration was large e.g., lots of sessions).
SecureCRT could hang or display output incorrectly when the output contained OSC RGB color substitution escape sequences.
When upgrading from a version of SecureCRT prior to 6.1, session logon actions were not migrated.
In the Quick Connect dialog, if all authentication methods were disabled for SSH2 and then an attempt was made to change the protocol to Telnet, a warning was displayed and the protocol was not changed.
When the session options "Shift forces local mouse operations" and "Send scroll wheel events to remote" were set, scroll wheel events with SHIFT pressed were sent to the remote system.
It was not possible to drag the file separator in vim.
The selection in a session could be lost when switching between tabbed sessions or when the cursor was repositioned to the same row as the selection.
If the Session Manager had "Auto Hide" set and focus was in an application other than SecureCRT, if the mouse was moved over the
Session Manager, it appeared to be activated, but clicking in the
Session Manager did nothing.
If the global options "Reuse disconnected tabs" and "Connect sessions in tabs" were off and the SecureCRT window contained a disconnected tab, when a new session was connected, it was opened in a new tab.
A highlight keyword list with the name "New..." could not be edited or deleted. The name "New..." is no longer allowed.
If a disconnected tab was reused and the new session had a different value specified for the scrollback lines, the value from the old session was used.
When the narrow font was being used, pressing the "Font" button for the Normal font showed the wrong font in the Font dialog.
SecureCRT did not produce the correct result for the vttest test "Test of autowrap, mixing control and print characters."
If SecureCRT started in tiled mode and then was switched to tabbed mode, the "Show button bar" session option was not honored.
If the windows transparency settings were change to values other than 255 (opaque), the settings were not honored when SecureCRT restarted.
Pass-through printing did not print Unicode characters correctly.
SSH2: If the host key database was on an offline cached network drive, SecureCRT was not able to save new host keys.
SSH2: The cached session password was not updated after a password change was forced by the remote system.
SSH2: The SHA-2 fingerprint of the public key was not correct when a pfx file was used as the public key.
SSH2: When attempting to connect to a session that specified PKCS #11 public-key authentication using the ActivClient DLL, the connection failed due to an error creating the signature during public-key authentication.
Windows: On a high-DPI (e.g., 4k) monitor, font scaling and session zooming did not work correctly.
Windows: On high-DPI monitors with scaling enabled, folders in the Session Manager could not be expanded or collapsed.
Windows: The Keymap Editor did not work correctly on high-DPI monitors.
Windows: The INI-file-only option to limit the taskbar preview thumbnails was not being honored.
Windows: If a session that toggled the display of the button bar or Command window was connected, the SecureCRT window resized and changed the session's geometry.
Windows: When using the Windows Classic theme, if the terminal window contained scrollback data, moving the Find dialog over it caused sections of the terminal window to be erased.
Windows: When the session database contained folders and one of those folders was selected in the Session Manager, if a session was created using the Quick Connect dialog, the session was not saved in the selected folder and any expanded folders were collapsed.
Windows: Attempting to set the port forward table using an array in a VBScript script failed.

New in SecureCRT 7.3.6 Build 963 (Dec 2, 2015)

New in SecureCRT 7.3.5 Build 903 (Sep 11, 2015)

New in SecureCRT 7.3.4 Build 839 (Jun 17, 2015)

New in SecureCRT 7.3.3 Build 779 (Apr 2, 2015)

New in SecureCRT 7.3.2 Build 752 (Feb 26, 2015)

New in SecureCRT 7.3.1 Build 685 (Dec 5, 2014)

New in SecureCRT 7.3.0 Build 657 (Oct 24, 2014)

New in SecureCRT 7.3.0 Build 642 Beta 5 (Oct 3, 2014)

New in SecureCRT 7.3.0 Build 633 Beta 4 (Sep 24, 2014)

New in SecureCRT 7.3.0 Build 622 Beta 3 (Sep 10, 2014)

New in SecureCRT 7.3.0 Build 611 Beta 2 (Sep 5, 2014)

New in SecureCRT 7.2.6 Build 606 (Aug 20, 2014)

New in SecureCRT 7.3.0 Build 597 Beta 1 (Aug 8, 2014)

New features:
Windows: Added support for regular expressions in keyword highlighting.
Added the ability to specify colors for keyword highlighting.
In keyword highlighting, the styles (reverse video, bold, and color) can be combined.
Added the ability to edit keywords used for keyword highlighting.
Added support for exporting and importing SecureCRT settings to and from XML, which makes it easier to copy settings from one machine to another.
Added a search filter to the session manager, which helps find sessions quickly, especially when a large number of sessions have been saved.
Added the ability to connect to a remote system through a named pipe.
Added the ability to script Kermit file transfers.
Added the ability to specify the substitution parameter %USERNAME% as a session username.
Added a new session option "Position cursor on left click" that allows the mouse to move the cursor to a different location.
Added a new session option "Enable alternate screen switching".
Added an option to disable the hover text for buttons on the button bar.
Added a new menu item "Close All Sessions" to the tab menu, which allows all sessions to be closed without closing the SecureCRT window.
Added a new global option "Exit SecureCRT when last session is closed" that specifies whether or not the SecureCRT window should be closed when the last session is closed.
Added a global option to swap ENTER and CTRL+ENTER in the command (chat) window.
Added the ability for the command (chat) window to be controlled independently in each SecureCRT window.
Changes:
Added the ability to store keys larger than 2048 bits in agent.
Added the ability to generate keys larger than 2048 bits.
When connecting a session, if there's an agent key associated with the session, it is tried first. This can help prevent a session from failing to connect because the maximum number of authentication retries was exceeded.
The MD5 and SHA-1 fingerprints are now displayed in dialogs that show host key information.
When multiple sessions are being edited, if a single expect or send string is changed in the session automated logon option, only the single string is changed in all the sessions. Previously, the entire expect/send block was written to the sessions.
Added the ability to send a disconnected session to a new window.
Log files are saved with a .log extension by default unless a different extension is specified.
Font information was added to the information stored in the personal data folder.
Bug fixes:
SecureCRT could crash if multiple sessions specified the same session as a firewall (i.e., jump host).
SecureCRT could crash when the send delay "Prompt" option was set and a large amount of text was pasted into a session.
SecureCRT could crash when several GNS3 sessions were connected in rapid succession.
SecureCRT could hang if a partial execute escape sequence was received.
When using mcedit (Midnight Commander editor), incorrect text was selected when switching between multiple screens or if the SHIFT key was down and the mouse moved, which caused incorrect text to be pasted.
If a session was resized and then another session was opened, the application window was changed to the size before the session was resized.
When a color scheme that was being used by two or more open sessions was changed from the Session Options dialog, only the active tab was updated to reflect the change.
If a button was mapped to the menu function CLEAR_SCREEN_AND_SCROLLBACK, if the SHIFT key was held while the button was clicked, only the current session was cleared.
If the system resolution was changed while SecureCRT was running, the font information in the Session Options dialog did not get updated.
TAPI: If sessions were copied from one machine to another and the the modem in the TAPI sessions did not exist, SecureCRT did not indicate that there was a problem when the session was edited and displayed a cryptic error when attempting to connect.
Windows: Deleting the same session from multiple instances of SecureCRT using the session manager could cause all the sessions to be deleted.
Windows: If the "Black" display theme was being used by SecureCRT and RDP was used to connect from another system to the local system and then closed, SecureCRT's title bar was missing.
Windows: When using the session manager, if the default session was changed to include a username and a session was connected, SecureCRT prompted for the username.

New in SecureCRT 7.2.5 Build 550 (Jun 6, 2014)

New in SecureCRT 7.2.4 Build 524 (May 2, 2014)

New in SecureCRT 7.2.3 Build 500 (Apr 2, 2014)

New in SecureCRT 7.2.2 Build 491 (Mar 20, 2014)

New in SecureCRT 7.2.1 Build 443 (Jan 17, 2014)

New in SecureCRT 7.2.0 Build 415 (Dec 13, 2013)

New in SecureCRT 7.2 Build 407 Beta 5 (Dec 6, 2013)

New in SecureCRT 7.2 Build 395 Beta 4 (Nov 20, 2013)

New in SecureCRT 7.1.3 Build 378 (Nov 14, 2013)

New in SecureCRT 7.2 Build 384 Beta 3 (Nov 7, 2013)

New in SecureCRT 7.2 Build 372 Beta 2 (Oct 23, 2013)

New in SecureCRT 7.2 Build 359 Beta 1 (Oct 9, 2013)

New features:
Windows: Added a Session Manager that can be used in place of the modal Connect dialog. The Session Manager can be in a pane in the SecureCRT window or can be an undocked modeless dialog.
Added a global option to store personal data such as usernames and passwords in a location separate from the rest of the session data, which allows personal data to be kept private while other configuration data is stored on a network drive or on the cloud so that it can be used on different systems or shared with colleagues.
Added the ability to zoom a session (increase or decrease the font size) using CTRL+ or CTRL+"+" or CTRL+"-".
Added a script object CommandWindow that provides access to the command (chat) window from a script.
Added Ymodem support to the FileTransfer script object, which allows Ymodem transfers to be scripted.
The script function Screen.Send() can be used to send text to the screen only by using a new optional parameter.
Added the ability to pass arguments to logon scripts.
Added a two-digit year log file parameter substitution "%y".
Added a session INI-file-only option "Ignore Shift Out Sequence" that prevents SecureCRT from going into graphics mode when Shift Out (\016) is received.
SSH2: Added support for SHA-2 MAC algorithms.
SSH1/SSH2: Added two new session INI-file-options "Use Global Host Key Algorithms" and "Host Key Algorithms" that allow the session to order and filter the global host key algorithms. The session host key algorithm list must be a subset of the global host key algorithm list.
Changes:
The "chat window" has been renamed to "command window".
The option to open sessions in a tab is on by default.
SecureCRT uses the Default session's background color as the background color of the application window at startup.
For Ymodem and Zmodem uploads, files are removed from the file list after they are successfully transferred.
The anti-idle options to send a string or protocol NO-OP can now be configured to an interval of less than 10 seconds.
The Xterm keymap now sends Esc[H and Esc[F for Home and End.
Pressing SHIFT+TAB sends "^[[Z" to the session when Xterm emulation is specified.
The user interface reflects that when the global option "Use trackable insertion caret" is set, the session option "Cursor style" must be set to "Vertical Bar".
SSH1/SSH2: Added the session option "Force session channel to close on disconnect" to the Session Options dialog.
Telnet: Added the option "Server requires bare CR" to the Connection/Telnet category in the Session Options dialog.
Serial: The default flow control was changed to none. This only affects new installations.
Bug fixes:
If a new session was created and the password was saved, the password had to be re-entered if the session was connected again without disconnecting the original session.
If authentication prompts were displayed in the terminal window, the Screen.Synchronous property did not work correclty.
If a tab was renamed manually, it reverted back to the original name after toggling between tabbed and tiled mode or if the session received an OSC_TITLE sequence from the remote system.
The Transfer menu was available during a transfer.
The "Send Zmodem" menu item was available on the drag and drop transfer menu when a folder was dragged.
SSH2: If the host specified for GSSAPI authentication was an IP address, SecureCRT hung during kexinit.
Windows: The vertical scrollbar in SecureCRT sessions did not work with Windows 8 and WindowBlinds.
Windows: If a connected session specified the "Windows" color scheme and the system colors were changed, the session did not reflect the system changes.

New in SecureCRT 7.1.2 Build 316 (Aug 9, 2013)

New in SecureCRT 7.1.1 Build 264 (May 31, 2013)

New in SecureCRT 7.1.0 Build 244 (May 3, 2013)

New in SecureCRT 7.1.0 Build 238 Beta 5 (Apr 26, 2013)

New in SecureCRT 7.1.0 Build 230 Beta 4 (Apr 12, 2013)

New in SecureCRT 7.0.4 Build 537 (Apr 4, 2013)

New in SecureCRT 7.1.0 Build 219 Beta 3 (Mar 29, 2013)

New in SecureCRT 7.1.0 Build 208 Beta 2 (Mar 15, 2013)

New in SecureCRT 7.1.0 Build 195 Beta (Feb 27, 2013)

New features:
Added support for dependent sessions so that a connection can be made to a jump host or SSH gateway before the session is connected.
Added support for the Kermit file transfer protocol. Binary and ASCII transfers are supported.
SSH2 on Windows: Added support for SHA1 in RSA signatures, which allows X.509 certificates to be used in FIPS mode and other settings where MD5 cannot be used.
A button action can be sent to all connected tabbed or tiled sessions by pressing SHIFT+ on the button.
Added a character send delay option to wait for a text prompt.
Added a new logging substitution variable "%P", which inserts the session's port.
Added the ability to copy ANSI text to the clipboard, which allows attributes such as color and font to be preserved on the clipboard.
Added support for sending Xterminal escape sequences for CTRL+ keys.
Added the ability to specify ANSI colors for individual sessions in addition to the global option.
Windows: Added support for the Wyse label line.
Changes:
Improved scrolling performance when the session options "Jump scroll" and "Minimize drawing" are set.
Changed the protocol NO-OP to send decimal code 241 instead of 0.
When the escape sequence "CSI ?3l" is received, the data is added to the scrollback buffer before the screen is cleared.
Bug fixes:
SecureCRT could crash when attempting to clone a session connected to a device that does not support multiple connections if prompts for both sessions were displayed at the same time.
If a tab was manually closed and then was closed by a script, SecureCRT crashed.
SecureCRT could crash if it was tunneling through a SOCKS proxy on a laptop and the laptop was closed.
The password prompt was displayed every time a host disconnected, due to the session timing out, and reconnected automatically.
The cursor went below the session window if the chat window was displayed and the number of session rows was larger than the session window height.
If a machine had two monitors and the main SecureCRT window was dragged to the second monitor and maximized, when a session with the inital position located on the first monitor was opened and switched to fullscreen mode, the main window got moved to the first monitor.
In the "Connect" dialog, if a new folder was given the same name as an existing folder except for different capitalization, after exiting and restarting SecureCRT, both folders were gone.
If a key was mapped to VT_KEYPAD_ENTER, the key did not work when the terminal was in newline substitution mode.
SSH2: The global option "Cache session password" was not honored for keyboard interactive authentication.
SSH2: If a session was configured to use password and X.509 public-key authentication, if the key was signed, but failed, the same key was sent again instead of sending the next key.
Windows: If a terminal session channel could not be opened because of a resource shortage, an error was displayed and the terminal area was not displayed correctly.
Windows: The application icon was not removed from the Program group during an uninstall.
Windows: If "Connect" was selected from the Activator and "Quick Connect" was selected from the "Connect" dialog, the connection was not made.

New in SecureCRT 7.0.3 Build 480 (Jan 18, 2013)

New in SecureCRT 7.0.2 Build 418 (Oct 26, 2012)

New in SecureCRT 7.0.1 Build 374 (Aug 29, 2012)

New in SecureCRT 7.0.0 Build 326 (Jul 4, 2012)

New in SecureCRT 7.0.0 Build 318 Beta 4 (Jun 20, 2012)

New in SecureCRT 7.0.0 Build 307 Beta 3 (Jun 6, 2012)

New in SecureCRT 7.0.0 Build 295 Beta 2 (May 23, 2012)

New in SecureCRT 7.0.0 Build 281 Beta (May 4, 2012)

New features:
Added the ability to tile sessions within the SecureCRT application window. Sessions can be tiled vertically, horizontally, or cascaded. Scripts can use the "Tab" object to work with tiled sessions.
Added the ability to start a built-in TFTP server when a session connects.
SSH2: Added the ability to skip authentication methods while authenticating.
When the mouse hovers over a button, the command the button is mapped to is shown as hover text.
Added the ability to map the items on the "Tools" menu to a button or key.
Added the ability to map "Always on Top" to a key.
Added support for the "Insert" key to the Wyse 50/60 emulation.
Windows: Added a global option to ignore the print screen (PrtScn) key being pressed.
Changes:
Improved the performance of the "Connect" dialog when the configuration is located on the network.
It is now possible to close the last tab.
The port can now be specified in the "Connect" bar on the toolbar.
The chat window history limit has been increased to 32,000 commands.
When scrolling back into the scrollback buffer, empty lines (such as from the "clear" command) are not shown.
Added a way to access buttons that were not visible on the button bar if the configured buttons did not fit in the window.
Added "Send Break" to the "Edit" menu, which sends a Telnet break.
If a change is made to the settings of a cloned session, the change is propagated to the other SecureCRT windows and/or sessions.
The first tabbed session's scrollbar settings are used for subsequent tabbed sessions so that all the sessions will have the same number of rows and columns.
When attempting to use Zmodem to transfer a file larger than 4 GB, an error is reported.
The installer now remembers the installation options from the previous install.
Kerberos delegation results are displayed in the trace output.
The script file location is displayed when a script cannot be opened.
The "Connect" dialog now has the same icons as the toolbar.
Changed the button labels on the dialog that is displayed when the default session is changed in order to make it harder to accidentally apply the changes to all sessions.
Telnet: When the session's IP address is IP4, it is displayed in the status bar.
When there are multiple tabbed sessions, only the active session is displayed in the Windows 7 task bar preview.
Bug fixes:
SecureCRT crashed when a script was run that sent an exit command to an SFTP tab.
SecureCRT crashed if a script called GetOption("[SSH2] Port") on a session that did not specify a firewall.
If a command was typed at the prompt, but ENTER was not pressed, and then the session was scrolled back to the oldest row and the top row was selected and ENTER was pressed, SecureCRT could crash.
SecureCRT crashed when the "Retain size and font" session option was set, the lines of scrollback was set to 0, the visible rows were less than the actual number of rows, the first several rows were not visible, and an escape sequence that erased a line was sent.
Xmodem transfers could hang at the beginning of the transfer.
If a host key hostname contained an escaped ".", it could not be saved.
When using mouse mode in vi, vim, or mc, there was a slight delay between clicking the mouse and the cursor being positioned at the mouse location.
When scripting was administratively prohibited, the "Script" menu was still available.
When the global option "Reuse disconnected tabs" was set and a session that had the "Show chat window" and "Sync view to size" options set was disconnected and then a session with "Sync view to size" enabled, but "Show chat window" disabled was connected, the number of rows in the session was not correct.
When a key was mapped to a function or arrow key that sent a multi-byte escape sequence, the mapped key sometimes didn't work.
The title bar setting in the "Default" session could be used to rename tabs using substitution parameters for "Quick Connect" sessions, but was not honored for saved sessions without a username.
The "Quick Connect" dialog sometimes used the default username or previously used username even though the username was empty.
The keyboard-interactive password prompt was displayed when the password was specified on the command line with the /PASSWORD flag.
If a log file contained a leading space, an error was reported.
The keyboard accelerator for "Clear Screen and Scrollback" did not work from a custom menu.
If there were two tabbed sessions and there was scrollback data in the second tab and then the second tab was disconnected and reused for a different session, the scrollback was not cleared.
When Zmodem was used to transfer a file larger than 2 GB, the progress information was not correct.
If /Log was specified on the command line and additional parameters such as session name or username were also specified, the /Log parameter was not honored.
If Connect() was called from a script and the option to suppress popups was set, it was not possible to detect failures by looking at error codes in crt.GetLastError and crt.GetLastErrorMessage.
SSH1/SSH2: If key re-exchange occurred during a transfer and "[email protected]" compression was being used, the session disconnected.
SSH2: Authentication failed when the server requested the keyboard-interactive method more than once.
If the Windows Input Method Editor (IME) was being used to input Korean characters and data was received, the IME was cancelled, causing the wrong character to be inserted into the session.
When a session name was longer than 32 characters, it was listed twice in the Windows 7 Start menu and taskbar MRU list.
On Windows 7, if the system Telephony service's startup type was set to "Disabled", a TAPI error was reported when attempting to create a session using the session wizard.
In the Chinese version of Windows XP and Vista, the font used for the title bar, menu, and status bar was smaller than the system font.
On Windows XP, the button bar dropdown sometimes displayed the button bar names in a larger than normal font.

New in SecureCRT 6.7.5 Build 411 (Apr 20, 2012)

New in SecureCRT 6.7.4 Build 354 (Feb 3, 2012)

New in SecureCRT 6.7.3 Build 292 (Nov 10, 2011)

New in SecureCRT 6.7.2 Build 229 (Aug 12, 2011)

New in SecureCRT 6.7.1 Build 188 (Jun 17, 2011)

New in SecureCRT 6.7.0 Build 172 (May 27, 2011)

New in SecureCRT 6.7.0 Build 164 Beta 5 (May 19, 2011)

New in SecureCRT 6.7.0 Build 153 Beta 4 (May 5, 2011)

New in SecureCRT 6.6.3 Build 412 (Apr 26, 2011)

New in SecureCRT 6.7.0 Build 137 Beta 3 (Apr 13, 2011)

New in SecureCRT 6.7.0 Build 132 Beta 2 (Mar 25, 2011)

New in SecureCRT 6.7 Beta 1 (Mar 9, 2011)

New features:
Linux versions for Ubuntu 10.x (32-bit and 64-bit) and Red Hat Enterprise Linux 5.5 (32-bit and 64-bit).
Added an optional connect bar, which allows a connection to be made by entering the host on the toolbar.
Added support for recording Python scripts.
Added the ability to add more than ten buttons to a button bar.
Added the ability to copy buttons from one button bar and paste them on another button bar.
Added the ability to move buttons within a button bar.
Added the ability to map a key or button to browse for a script to run.
Added the ability to configure the double-click tab action to be "Clone Tab in New Window".
Added an option to the Connect dialog to sort sessions logically, which is helpful when session names contain numbers.
In the Session Options dialog, added ability to sort columns in the Connection / Port Forwarding category.
Added support for in-line composition of IME characters so that IME characters are inserted into the session window as they are typed.
Added the script function FileOpenDialog() that displays the file browser and returns the selected file.
Added the script function ScriptFullName() that returns the full path and filename of the currently running script.
Added an optional parameter to the scripting function Connect() that allows pop-up messages to be suppressed.
Added the ability to specify a listening IP address when setting up a local or remote port forward from the command line.
Added a global INI-file-only option "Script MRU Count" that allows the number of scripts displayed in the recently used script list to be specified.
When the global INI-file-only option "Single Instance" is set and SecureCRT is already running, shortcuts that use the /S flag now open the specified session in a new tab.
Windows: Environment variables can be specified when assigning a "Run Script" or "Launch Application" function to a button or key.
Changes:
Line and character send delay settings are now honored for buttons and keys mapped to send strings.
When pasting text into SecureCRT, LF is converted to CRLF.
The session option "Enforce X11 Authentication" can now be set in the Session Options dialog. Previously, it had to be set manually in the session .INI file.
The button and keymap Menu function MENU_TAB_NEXT now has the same behavior as pressing and releasing CTRL+TAB. The Menu function MENU_TAB_PREV now has the same behavior as pressing and releasing SHIFT+CTRL+TAB.
If a script is already running and an attempt is made to run another script, a message is displayed.
Windows: Entering the license data now registers the application for all users instead of only for the current user.
Bug fixes:
If SecureCRT closed while a dialog was being displayed, it crashed.
If an escape sequence that sent a large file (1 MB or larger) was running and SecureCRT was exited during the send, it crashed.
If a script set a session's columns to be larger than the maximum number of columns and then that session was used, SecureCRT crashed.
SecureCRT could crash if it was in the process of closing and a script attempted to access an object that no longer existed.
SecureCRT could crash when a second instance was started.
SecureCRT terminal locked up after exiting a remote command such as "vi" or "man" if the window was resized while the command was running.
Python scripts that contained a Unicode character in the script name could not be run.
In some cases, screen reading software such as JAWS was not able to track the cursor when the cursor style was set to "Block". If the "Use trackable insertion carat" option is set, the "Vertical Bar" cursor style is now used.
If a key or button was mapped to launch an application that did not have an ".EXE" file extension and an argument was specified, the specified argument was not saved.
If a session used ANSI color and a color scheme and the scrollback buffer contained text, if ANSI color was disabled and re-enabled, some characters in the scrollback buffer were displayed using incorrect foreground and background colors.
Highlighted text sometimes flickered.
In the Connect dialog, if the right mouse button was clicked on title bar or toolbar, the context menu was not displayed at the mouse cursor.
Telnet: When an unrecognized IAC SB option was received, garbage was displayed in the session.
SSH1/SSH2: On Windows Vista and Windows 7, if "localhost" was specified for port forwarding, it resolved to an IPv6 address, which caused the port forward to fail.
SFTP: In the SFTP tab, when an "ls" command was issued and the files had long names, the spacing of the output was not correct.
SFTP: In the SFTP tab, tab completion did not work with character encodings such as utf-8, koi8-r, and OEM=cp866.
Windows: When a Perl script was specified on the SecureCRT command line, an error was thrown if the script called Crt->Quit().

New in SecureCRT 6.6.2 Build 350 (Feb 1, 2011)

Changes:
SSH2: Added support for reading AES-128 public keys.
Bug fixes:
If multiple instances of SecureCRT were running and they were all closed at the same time, the file containing the global settings could get corrupted, which caused SecureCRT to attempt migration the next time it ran.
If the Xmodem sent packet size was set to 1024 bytes and a file that was 1024 bytes or larger was sent using Xmodem, SecureCRT could crash.
Under certain conditions, a race condition between terminating a script and closing SecureCRT could cause a crash.
SecureCRT could crash if shortcut keys were used to select invalid operations in the Connect dialog.
During initialization, if SecureCRT failed to acquire a Cryptographic Context, SecureCRT crashed when it closed.
When attempting to connect using a SOCKS proxy, if the SOCKS server replied fast during negotiation, it could cause messages to be received out of order, which caused the connection to fail.
When a local port forward contained an IPv6 address, SecureCRT was not able to save the host key.
The session option to disable pass-through printing was not being honored.
If two tabbed sessions were opened, but not connected, when the first tab was made active, its status indicator showed that it was connected.
If a Quick Connect or local shell (Mac only) session was connected and closed and then the default color scheme was modified, a new Quick Connect or local shell session did not use the new color scheme.
If a remote login banner contained a high-bit character, SecureCRT stopped displaying the banner when it hit that character.
After loading an invalid keymap, pressing CTRL+TAB to switch between tabs no longer worked.
Attempting to save a recorded script to a location that was not writable failed silently, causing the script to be lost.
No screen painting occurred while crt.Sleep() executed in a script.
The session option "Keymap v3" could not be accessed from a script.
The script function crt.Session.Connect() always opened a new tab even when the "Reuse disconnected tabs" option was set.
In Python scripting, the failSilently parameter in the ConnectInTab function in the Session object was not implemented.
The script function SendKeys() did not send text to the correct tab if the tab was switched while the script was running.
Selecting "Check for Updates" from the Help menu launched the VanDyke forums.
Serial: If a session was disconnected during a Zmodem upload, SecureCRT could crash.
Serial: SecureCRT could lock up if the session was disconnected during the Zmodem transfer.
Telnet, Raw: If an invalid port was entered in the New Session wizard and the Back button was pressed, SecureCRT crashed.
SSH2: It was not possible to specify the same port for port forwarding even if a different local IP address was used.
In some cases, the initial position of a session was different when the session was disconnected and then connected again.

New in SecureCRT 6.6.1 Build 289 (Nov 5, 2010)

New in SecureCRT 6.6.0 Build 278 (Oct 22, 2010)

New in SecureCRT 6.6.0 Build 257 Beta 5 (Oct 1, 2010)

New in SecureCRT 6.6.0 Build 247 Beta 4 (Sep 17, 2010)

New in SecureCRT 6.6.0 Build 222 Beta 2 (Aug 18, 2010)

New in SecureCRT 6.5.4 Build 555 (Aug 11, 2010)

New in SecureCRT 6.6.0 Build 206 Beta 1 (Aug 4, 2010)

New features:
SecureCRT for Mac OS X delivers right out of the gate, with reliable, mature terminal emulation, tabbed sessions, security, powerful session configuration, and printing support.
SecureCRT for Mac OS X adds support for the local command shell.
Added embedded support for the Python scripting language.
New Raw protocol mode allows for no (or little) interpretation of data from the remote system, which is helpful for troubleshooting.
Added a "Send Binary" transfer option.
A unique log name is automatically generated when the specified name is in use (e.g., cloned or SFTP sessions).
Arguments can be passed to scripts from buttons and mapped keys.
Added new double-click options to tabs; these options are "Send Tab to New Window" and "Reconnect Tab".
On Windows, the button bar can be positioned at the top of the SecureCRT window.
Added an option to kill the tab created by the ConnectInTab script function when it fails to connect to a host.
SSH1/SSH2: Added support for the "null" host-key algorithm for GSS-KEX as specified in RFC 4462.
Changes:
Added "Manage Agent Keys" to the Tools menu.
When the "Trace Level" is set to 9, the password is automatically redacted from the trace output.
In the Quick Connect dialog, if the protocol is changed from SSH1 or SSH2 to any other protocol, the port is changed to the default port.
In the Global and Session Options dialogs, the options in the Advanced Printing category were moved to the Printing category.
Bug fixes:
If "\p" was specified in an anti-idle string, SecureCRT could crash after the string was sent.
If a tab completion was cancelled on a slow server and then the connection was closed, SecureCRT could crash.
When sessions were cloned using "Clone in New Window", configuration information could potentially be written at the same time, causing SecureCRT to crash.
SecureCRT opened an SFTP channel when opening the Session Options dialog, which could cause the active session to disconnect.
If SecureCRT was launched more than once on the same machine using different configuration folders and a session that existed in one configuration, but not the other, was opened in the Activator, the instances of SecureCRT that did not contain the session crashed.
Quick Connect sessions where the host was an IPv6 address could not be saved.
The blink attribute was not honored when the SecureCRT window was maximized and the cursor was outside the session's original geometry settings.
Dismissing the Find dialog in a different tab than it was started from could cause output to suspend.
When the option "Only show tabs when there are more than one" was enabled and a second tab failed to connect, the tab bar was not displayed.
When multiple sessions were edited at the same time, port forward changes were not always saved correctly.
In the Printing category in the Global and Session Options dialogs, invalid margins could be saved.
Cloning a non-SSH2 session in a script caused the script to hang.
In the ReceiveXmodem script function, the "Download" folder was not honored.
If the scripting clipboard format was set to an invalid format, the last error was not set correctly.
The CRT.Session.Connect script method did not allow a script to capture in-terminal SSH2 username or password prompts.
If SecureCRT was displayed on a second monitor when it exited and only one monitor was available the next time it ran, SecureCRT was still displayed on the second monitor.
If full-screen mode was entered before a session was connected and then full-screen mode was exited, the SecureCRT window was displayed partially off screen.
On the 64-bit version of Windows 7, tab preview functions did not work.
On Windows, when large font (120 DPI) was used, text on some dialogs was truncated and buttons on the Keymap Editor dialog were cut off.
If an X11 error occurred, the error message was displayed behind the SecureCRT window.
Serial: The XOFF setting was not being honored, which could cause input to go to the wrong session when more than one Serial session was connected.
SSH1/SSH2: If an accept host-key prompt was displayed during key exchange and the protocol NOOP anti-idle expired, the SecureCRT window could hang.
SFTP: SecureCRT crashed when trying to open an SFTP tab if the remote server did not support SFTP.
SFTP: Memory was leaked when SFTP tabs were closed.

New in SecureCRT 6.5.3 Build 490 (May 12, 2010)

Changes:
After changing the selected button bar in the drop-down list, focus is returned to the active session.
Bug fixes:
SecureCRT could become unresponsive when switching from an RDP session to a local session.
Fixed threading issues that could cause SecureCRT to crash.
SecureCRT could crash when it was in full screen mode and random data was received.
SecureCRT crashed if a logon script called Disconnect() followed by Connect().
With multiple SecureCRT windows open, toggling the chat window, button bar, etc. caused the terminal size to get smaller and could cause SecureCRT to crash.
SecureCRT could disconnect from a Cisco router if data was sent before the shell was ready.
SecureCRT could crash when attempting to connect to a session using a hostname that could not be resolved.
Enabling GB18030 Simplified Chinese character encoding caused the session to stop displaying output.
The performance of "Send ASCII" decreased significantly as the number of lines being sent increased and SecureCRT could appear to be hung.
Line-drawing characters were not displayed correctly with SCOANSI emulation.
Artifacts were sometimes left on the screen when ClearType was enabled.
If a non-qualified path was specified for the log file, SecureCRT failed to log and did not report an error.
If the Close button was pressed a second time for a session to a slow or unresponsive server, the connection was orphaned and would not close until SecureCRT exited.
If the button bar drop-down list was selected, typing the first letter of a button bar name caused the button bar height to increase.
If the session's tab was clicked, focus was not placed in the terminal area of the session.
The arrow keys could not be used to navigate context menus.
SSH1/SSH2: SecureCRT could crash if a session was disconnected during user authentication.
SSH1/SSH2: After changing a port in the port forwarding settings in the default session and applying it to all sessions, the
setting was removed altogether.
SSH1/SSH2: If a session was connected more than once and the session's port forward options were modified, the changes were not saved.

New in SecureCRT 6.5.2 Build 446 (Mar 11, 2010)

New in SecureCRT 6.5.1 Build 410 (Jan 22, 2010)

New in SecureCRT 6.5.0 Build 380 (Dec 10, 2009)

New in SecureCRT 6.5.0 Build 371 Beta 5 (Dec 3, 2009)

New in SecureCRT 6.5.0 Build 358 Beta 4 (Dec 3, 2009)

New in SecureCRT 6.5.0 Build 346 Beta 3 (Oct 29, 2009)

Changes:
Restored previous behavior of allowing the password to be saved
regardless of the "Auto Save Options" setting.
Bug fixes:
It was possible for SecureCRT to crash when attempting to select
text near the end of a line.
SecureCRT could crash when configuring a private key for a
session.
SecureCRT could crash when a tab was closed if the Session
Options dialog had been opened after connecting to a session.
If the INI-file only option "Force Close On Exit" was set and
an SSH2 session was connected and cloned, if one of the tabs was
closed, SecureCRT crashed on exit.
Displaying certain Unicode sequences could cause SecureCRT to
hang.
Scrolling Unicode data was much slower than scrolling non-Unicode
data.
The underscore character was included in the list of default
delimiters.
If the user had full write access to the root drive and
attempted to log to a file in the root drive, an "Access Denied"
error was reported.
Send ASCII ignored the end-of-line characters if the text file
contained end-of-line characters other than CRLF.
Clicking the red "X" in the Windows 7 taskbar peek for SecureCRT
did not close SecureCRT.
On Windows 7, if ANSI color was on and a tab subsequent to the
first tab was connected, the terminal area in the new tab
flickered, briefly showing lines of different colors.
When the JAWS screen reading software was used in cursor mode,
if output that contained blank lines was displayed in SecureCRT,
using the arrow keys to move the mouse cursor over the blank
lines caused the cursor to jump over several blank lines instead
of moving one line at a time.
After upgrading to 6.5, if a custom menu and toolbar XML file
from version 6.2 or earlier existed, the ALT+B accelerator to
connect in a tab no longer worked.
If the global option "Show confirm disconnect dialog" was off
and a session was connected and cloned, then the cloned session
was closed using the close button on the tab, window decorations
such as menus and toolbar buttons did not receive focus when
mousing over them.
Output that did not wrap when printed under Windows XP wrapped
when printed under Windows 7 and Vista.
Bold characters were not printed as bold characters.
SSH2: Attempting to use a private key without a corresponding
public key caused SecureCRT 6.5 beta 2 to crash.
SFTP: SecureCRT could crash when downloading a directory that
contained thousands of files.

New in SecureCRT 6.5.0 Build 335 Beta 2 (Oct 16, 2009)

New features:
The chat window can be resized by dragging the splitter bar.
Changes:
SSH2: When an RSA key is used for authentication, only the
private key is required, which makes it easier to use Amazon
EC2 keys.
If a custom menu (.mnu) file specifies the "Office 2007" theme,
which is not available in SecureCRT 6.5, the "Office 2003" theme
is put in the menu instead.
Bug fixes:
If the Activator was exited while the Global Options dialog was
open, SecureCRT crashed.
SecureCRT crashed if a session that specified a non-existent
keymap was cloned or opened a second time.
If the /NOMENU option was specified on the command line, a
"Failed to create empty document" error was reported.
For Ymodem transfers, 128-byte packets were sent when Ymodem-1k
option was specified.
The Delete, Home, End, PageUp, and PageDown keys did not work in
the chat window.
If the paste on middle button option was set and a middle button
press was simulated by pressing the left and right mouse buttons
together, the context menu was displayed.
If the tab bar was not displayed when SecureCRT started and then
a session was connected and the tab bar was displayed, the status
indicator icon did not have the correct status.
When the status indicators were shown as background colors, if
there were more tabs than could fit across the window and a tab
was closed, the tab bar was not redrawn correctly.
If the toolbar was changed to a custom toolbar and then back to
the default toolbar, the "Toolbar Options" drop-down arrow was
no longer displayed.
If a custom menu (.mnu) file was specified and SecureCRT was
restarted, then the custom menu was cleared and SecureCRT was
restarted, the toolbar icons were not displayed correctly.
It was possible to close a locked session from the Windows 7
taskbar.
If SecureCRT was minimized, the live preview in the Windows 7
taskbar displayed a busy circle until it eventually failed to
get a thumbnail bitmap and displayed a default icon.
If SecureCRT connected to multiple sessions at start up and then
was minimized, the Windows 7 taskbar only contained a
thumbnail image for one of the tabbed sessions.

New in SecureCRT 6.5.0 Build 324 Beta 1 (Oct 2, 2009)

New features:
Unicode support was improved in the following areas: character
sets from multiple languages can be viewed in a session, display
of right-to-left reading order languages, UTF-8 characters can
be mapped in the Keymap Editor, Send/Receive ASCII works with
UTF-8 data, UTF-8 filenames can be used in the SFTP tab,
pass-through printing supports UTF-8 data, and better behavior
with scripts that use combining marks to compose characters.
In the Session Options dialog, the list of character encodings
displays all the encodings supported by the system.
Added an option that allows words to be specified in a list so
that they can be highlighted as they appear in the session.
An inactivity status notification option can be set for tabbed
sessions so that activity can be monitored in tabbed sessions
other than the current session.
There are new display settings for tab status indicators, which
are icons and tab background color.
The tab bar position can be set to the bottom of the SecureCRT
window.
When a session is locked, a locked icon is displayed on the tab
unless the "Color rectangles" status indicators are used.
SecureCRT has several new Windows display themes.
If a file is dragged from MS Explorer or other OLE-enabled
application into a connected SecureCRT session, it can be
transferred using ASCII, Xmodem, Ymodem, or Zmodem.
Added a global option that allows URLs to be opened by
CTRL+clicking them.
A new session option allows mouse wheel scroll events to be
sent to the remote application.
A new script function GetActiveTab returns the currently active
tab.
Added the ability to wait for a case insensitive string in a
script. The functions WaitForString and WaitForStrings take an
optional parameter to specify that the case should be ignored.
Additionally, the property IgnoreCase has been added to the Screen
object so that this can be set globally.
Added a script function SetStatusText that allows the status
bar text to be set from a script.
The script functions SetOption and GetOption now allow encrypted
passwords to be used in a script.
A command-line parameter /SESSION_FOLDER allows all the sessions
in a folder to be connected when SecureCRT starts.
A command-line parameter /EncryptedPassword has been added, which
allows an encrypted password to be specified on the command line.
SFTP: Dragging a file from MS Explorer or another OLE-enabled
application initiates a put command on the file.
Changes:
Increased scrolling performance when large amounts of text are
output to the session.
The following changes were made to the button bar: only
configured buttons are displayed, the button width is determined
by the button label, and the button bar menu is now on the left
side of the bar.
The "Semaphore timeout" error is now displayed in the session's
trace output instead of a message box.
The maximum value that the global maximum columns option can be
set to is now 32,000.
Modified the script function LogFileName so that if the log
filename contains parameter substitutions and logging is on,
the name of the file currently being logged to is returned.
Added a "Start Upload" button to the Zmodem Upload List dialog.
The character encoding restrictions on the vt100 font have been
removed.
In the Map Selected Key dialog, pressing the Default button
removes the entry from the keymap file.
In the Keymap Editor dialog, pressing ALT+O closes the dialog.
The close button now appears on the tab itself instead of to the
right of the tab bar.
Serial: The baud rate is now displayed in the status bar.
Bug fixes:
If data being sent using Send ASCII contained a null character,
nothing after the null character was sent.
Zmodem transfers did not complete when attempting to download
a zero-byte file.
The Xterm command "Use Alternate Screen Buffer" did not work.
The anti-idle string was not sent when a session was locked.
If a session was locked, the double-click tab action was still
honored.
When a session was started from the Activator, the new session
window appeared behind other application windows.
If a session without a username was edited while it was connected,
the username entered during authentication was saved to the
session.
If multiple sessions were being edited and a port forward was
added or deleted, only the first session was modified.
If one tabbed session was showing the button bar and another
tabbed session was not, then the second tab was moved to the
first position and then back and the window was resized, the
number of columns would increase when the mouse was released.
The number of lines specified for the scrollback buffer of the
first tabbed session was also used for the other tabbed sessions.
The "Upon Disconnect" custom log data was written twice to the
log file.
Exiting Activator while a SecureCRT session was locked left a
SecureCRT process running that could only be accessed through
the Windows Task Manager.
If the configuration folder's path had a trailing backslash,
sessions could not be connected from the Activator or from
SecureFX (if it was installed).
When %I was specified as a variable in the title bar session
option, it was not replaced with the IP address.
If the color scheme attributes were changed while the "ANSI color"
and "Use color scheme" options were set, the "Overstrike bold"
attribute was not changed.
SecureCRT had to be restarted for ANSI color table changes to take
effect.
The locked status of a tabbed session was not displayed correctly
in the status bar until the mouse moved over the toolbar or menu
bar, or the mouse was clicked in the session window.
If a window other than SecureCRT had focus and Connect was
called from a script, the SecureCRT window could get focus.
If the active tabbed session was disconnected, text could not
be pasted into the chat window.
If the installer was run in silent mode and an answer file that
could not be found was specified on the command line, a dialog
was displayed.
SecureCRT offered to make itself the default Telnet handler even
when the Telnet protocol DLL was not available.
RLogin: Sending window size messages to the server when they had
not been requested could cause garbage to be displayed in the
session.
Serial, TAPI: Zmodem transfers over Serial or TAPI did not switch
into and out of binary mode correctly, which could cause the
transfers to hang or transfer the same file repeatedly.
Serial: When a button was mapped to send a string of non-printing
octal characters, the order of the characters was sometimes
swapped when they were sent.
SSH1/SSH2: In the Enter SSH Username dialog, if the Save
username check box was checked and the Auto Save Settings
option was off, the username was not saved.
SSH2: In the Key Generation wizard, if the specified path for the
key contained two or more folders that did not exist, they key
could not be saved.

New in SecureCRT 6.2.3 Build 313 (Sep 11, 2009)

New in SecureCRT 6.2.2 Build 263 (Jul 2, 2009)

New in SecureCRT 6.2.1 Build 215 (Apr 29, 2009)

New in SecureCRT 6.2.0 Build 183 Beta 3 (Mar 19, 2009)

New in SecureCRT 6.1.4 Build 489 (Feb 24, 2009)

New in SecureCRT 6.2.0 Build 162 Beta 2 (Feb 18, 2009)

New in SecureCRT 6.2.0 Build 147 Beta 1 (Jan 30, 2009)

New features:
A native 64-bit Windows version is available.
Multiple sessions can be selected and edited from the Connect
dialog. Only the changed fields will be applied to the
selected sessions, which allows specific settings to be
changed for a group of sessions.
There is a new option to remember which sessions were open the
last time SecureCRT ran so that they can be launched the next
time the application runs.
Added an option to create a new log file at midnight, which
can be used to do automatic log rotation.
Added support for creating folders when a log file path is
specified that does not already exist, which allows parameter
substitutions to be used in folder names for log file paths.
Added a command-line parameter /LOG, which allows a log file to
be specified on the command line.
A blank password can be used to lock a session, which makes it
easier to prevent accidental typing in sessions.
SSH2: Added support for PKCS#11, allowing a Cryptographic Token
Interface to be used for smart-card authentication.
SSH2: In the Activator, agent support has been enhanced by
allowing keys to be explicitly added and removed.
SFTP: Added support for recursive remove (rm -r).
SFTP: Added support for the flags -a and -d to the ls and lls
commands.
Changes:
Empty cells are not stored in the scrollback buffer, which in
most cases, significantly reduces the amount of memory used by
a session.
The default Maximum columns setting has been increased to 256.
The default download, upload, and public key generation folders
have been changed to "My Documents". Under Vista, the default
download folder is the user's Download folder. Only new
installations are affected.
When SecureCRT and SecureFX are integrated, if the SecureFX
button on the SecureCRT toolbar is pressed and the current
session does not have a valid file transfer protocol
specified, a more informative message is displayed.
Serial: Added support for changing the baud rate of a connected
session.
SSH1/SSH2: Added support for specifying a password in the
Session Options dialog.
SSH1/SSH2: When creating an identity file, moving the mouse is
no longer required to generate random data.
Bug fixes:
A script that called crt.Close immediately after calling
crt.Screen.Send could cause SecureCRT to crash.
Connecting multiple sessions in tabs from a script sometimes did
not work correctly and some sessions hung or did not connect.
If the first tabbed session used the vt100 font, a session
that used UTF-8 encoding could not be cloned.
The terminal dimensions were not updated when tabs were dragged
between windows of different dimensions.
After exiting a session of vi that changed the foreground and
background colors, the foreground and background colors were not
restored correctly.
In some cases, the scrollbar was in the wrong position after
switching between tabbed sessions.
When downloading a file that contained an illegal character
such as ":" using Zmodem or Ymodem, the file name was truncated
at the illegal character. Illegal characters are now replaced
with "_".
If a firewall was specified on the command line and the firewall
name contained a space, it was not used.
If the "Auto Save Options" setting was off and a value was
changed in the Global Options dialog, if the Global Options
dialog was re-opened, the change was not reflected in the
dialog.
SecureCRT had to be restarted in order for changes made to the
Default session to be honored in Quick Connect.
If a session was deleted while it was connected, the session was
added to the session database after it was disconnected.
If the "Retain size and font" option was set and the window was
resized, under certain circumstances, some lines did not have
the correct background color.
If a firewall failed to connect and the "Auto reconnect" option
was set, a new firewall authentication dialog was displayed
every second.

New in SecureCRT 6.1.3 Build 423 (Dec 3, 2008)

New in SecureCRT 6.1.2 Build 409 (Nov 7, 2008)

New in SecureCRT 6.1.1 Build 383 (Oct 3, 2008)

- If the auto-reconnect option was set for a session and the
connection was lost, an error dialog was displayed. The 5.5
behavior of not displaying a dialog was restored.
- If the session option "Display logon prompts in terminal window"
was not set and a logon script was specified, the script was
started before the connection was established. The 6.0 behavior
of starting the script after the connection is established was
restored.
- Logon scripts were run when the administrative option to disallow
scripts from being run in SecureCRT was set.
- If the global option "Show confirm disconnect dialog" was set and
multiple sessions were open in different windows, exiting the
Activator could cause SecureCRT to crash.
- SecureCRT crashed when cancelling out of the select log file
dialog if the session tab no longer existed.
- In the Connect dialog, doing a Find Next after deleting a session
that had been found using Find caused SecureCRT to crash.
- In the Global Options dialog, on the Firewall page, double-
clicking the empty space below the firewall list or pressing the
DEL key when no firewall was selected caused SecureCRT to crash.
- After answering "No" to the confirm disconnect dialog, SecureCRT
became unresponsive.
- Under certain circumstances, if there were multiple SecureCRT
windows and the menu bar was toggled, SecureCRT could become
unresponsive.
- After selecting text in the scrollback buffer using a triple-
click, it was no longer possible to select text in the scrollback
buffer.
- If the SecureCRT window was maximized after scrolling up, garbage
was displayed in the session window.
- If an "exit" command was sent to a session in a script and then
another connection was immediately attempted, it could cause the
script to hang.
- If a session was connected using the Session.Connect(/s )
scripting method, the initial position specified in the session
options was not honored.
- SSH2: The TCP connection associated with a dynamic port forward
could get stuck in a CLOSE_WAIT state after the session was
disconnected.
- SSH2: Under certain circumstances, dynamic port forwarding was not
started when a session was connected.
- SSH1/SSH2: If the session option "Start log upon connect" was set
and no log file was specified, when connecting to the session,
after entering the password, focus went to the session window
instead of the Select Log File dialog.
- Global Secure Shell configuration information was not being
migrated.
- If two sessions had the same name, hostname, and username, they
were combined during migration, but only the terminal protocol
was set.

New in SecureCRT 6.1.0 Build 349 (Aug 22, 2008)

New in SecureCRT 6.1 Beta 4 (Jul 31, 2008)

New in SecureCRT 6.1 Beta 3 (Jul 25, 2008)

New in SecureCRT 6.1 Beta 3 (Jul 18, 2008)

New in SecureCRT 6.1 Beta 2 (Jul 3, 2008)

New in SecureCRT 6.1 Beta 1 (Jun 20, 2008)

New features:
Added the ability to search sessions and folders in the Connect
dialog, which supports searching for a session name, hostname,
folder name, or a keyword in the description.
Added items to the File menu to reconnect all disconnected
sessions and disconnect all connected sessions.
Added support for an unlimited number of automated logon
Expect/Send sequences and the ability to delete and reorder
the sequences.
Several example VB scripts are installed, which demonstrate how
to use SecureCRT's scripting support.
Added scripting support for sending special keys such as
function keys, control keys, and other special characters,
which makes it easier to write scripts that are protocol
and emulation independent.
Added Clipboard scripting functions provide access to the
current selected text and also to available Clipboard data,
which allows setting up actions such as running a script
that uses the contents of the Clipboard to send a command
to the session, or selecting text in the session and running
a script which launches a web browser to google that text.
Added scripting support for accessing session options, which
makes it possible to do operations such as configuring a session
before connecting and converting session information stored in a
file to saved sessions.
Added error handling methods to the Application scripting
object. The new methods GetLastError and GetLastErrorMessage
provide flexibility to how errors are handled in scripts.
The script method Connect can be called without arguments in
order to reconnect a session.
SSH1/SSH2: Added an option for authentication credentials to be
entered in the terminal window, which allows Secure Shell logons
to be scripted using the Expect/Send strings or "Logon script"
option found in the Session Options dialog.
SSH1/SSH2: The username and password can be saved when using
keyboard-interactive authentication, streamlining the logon
process.
SSH1/SSH2: Added a session option to execute a remote command
after connecting.
SFTP: Added a "view" command which downloads the specified file
and opens it in the default editor or appropriate application.
SFTP: If the remote server is VShell 3.5 or later, there is a
"su" command in the SFTP tab that allows you to become a
different user.
Changes:
When the "Single Instance" and "Launch New Windows in a
Separate Process" options are set, sessions cannot be opened in
a separate window.
The serial port can now be changed in the Default session.
Added read access to the crt.FileTransfer.ZmodemUploadAscii
property.
SSH2: The option "Enable OpenSSH agent forwarding" can be
specified on a per-session basis.
Bug fixes:
When the session option "Retain size and font" was set, if
the window was resized to be smaller than the number of
logical rows, it was not possible to scroll to the rows that
were cut off.
If a session was maximized and the "Synchronize view to size"
option was set, if the session was sent to a new window, the
logical rows and columns in the new window were incorrect.
Unicode output was not displayed correctly in a tabbed session
other than the first tab.
Under certain circumstances with SecureCRT maximized, text
could be cut off when switching between tabbed sessions.
Opening a new window while in full screen mode caused the new
window to appear partially off screen.
Under certain circumstances, a second SecureCRT window for an
existing session was cascaded when it shouldn't have been.
If two sessions with different initial positions were connected,
only the initial position for the first session was honored.
If the "Auto reconnect" option was set and authentication was
cancelled by the user, the session attempted to auto reconnect.
Under certain circumstances when the "Auto reconnect" option
was enabled, a session attempted to reconnect even though its
associated tab had been closed.
When the "Save expanded folder state in connect dialog" option
was set and a session in a folder was renamed in the Connect
dialog, it caused other folders to be expanded.
It was not possible to map a key or button to "Trace Options"
or "Raw Log Session".
The recent scripts menu item MENU_SCRIPT_MRU_FILE1 did not work
when used in a custom .MNU file.
In a script, certain crt.Screen.ReadString syntax errors could
result in a crash.
In a script, if a Connect call was made immediately after a
Disconnect call, SecureCRT could think the session was not
connected.
Under certain circumstances, the line number reported when a
script was cancelled was incorrect.
Paste output did not continue if a WaitForStrings script method
matched something in the pasted text.
SSH2: SecureCRT could crash when web traffic was forwarded
through Firefox's Foxy-Proxy.
SSH2: When a certificate from a CAPI store was used to
authenticate, agent forwarding did not work.
SFTP: On some platforms, such as rhel5 and rhel4-64, wildcard
(ls -l *) file listings were returned in the wrong order.
U3: Configuration settings were uninstalled when the U3 version
was uninstalled.

New in SecureCRT 6.0.2 (Apr 25, 2008)

Changes:
Dot files, such as ".svn", that are in the configuration folder no longer displayed in the Connect dialog.
When the administrative option to disable all scripting is on,
scripts cannot be recorded.
Added the global .INI-file-only option "Focus Does Not Affect Blink" that allows text with the blinking attribute set to blink when the SecureCRT window does not have focus.
SSH2: The "Enable OpenSSH agent forwarding" option is now off by default. This only affects new installations.
Bug fixes:
When there was a single tab, sending that tab to a new window multiple times could cause SecureCRT to crash.
Under certain circumstances, attempting to modify a session with a logon script could cause SecureCRT to crash.
If the File menu was opened and there was not enough room for it to be displayed, SecureCRT crashed.
If the context menu was displayed for an inactive tab with the "Close on disconnect" option set and the tab was disconnected while the menu was displayed, selecting a menu item other than
"Close" caused SecureCRT to crash.
The status bar was being updated more than necessary, which increased CPU usage.
Under certain circumstances, sessions that were disconnected could not be reconnected.
Pressing CTRL SHIFT V did not perform a paste operation.
After using Print Setup to select a different printer, printing
no longer worked.
The option not to display the "Check for Updates" dialog was
only saved if the "Auto Save Options" option was set.
In a script, if a disconnected tab was reconnected, it was
connected in a new tab.
In a script, the ConnectInTab method did not honor the "On Error Resume Next" statement.
If SecureCRT and SecureFX were installed separately, but used the
same configuration folder, when a session was created or modified, the protocol for the other application was set to None.
Accelerator keys defined in custom menu .MNU files were not
being honored.
If a custom menu .MNU file contained more than 1000 items, it
could not be loaded.
Under certain circumstances, the installer incorrectly reported
a "file in use" error, which prevented the application from
being installed.
Silent installs that specified an ANSWERFILE containing a
parameter substitution did not work.
Under Vista, if an MSI installer was used, the default
installation folder was in "Application Data" instead of
"Program Files".
Telnet: If a session was saved in the maximized state, the rows
and columns were not set correctly on the host the next time it
was connected.
SSH2: If a proxy such as Proxycap or Foxy-Proxy was being used,
SecureCRT crashed when attempting to connect a session that did
port forwarding.
SSH2: SecureCRT could crash if a session was closed while
attempting to port forward to a destination that was not
listening or a host that did not resolve.

New in SecureCRT 6.0.1 (Feb 21, 2008)

New in SecureCRT 6.0.0.168 Beta 5 (Jan 8, 2008)

New in SecureCRT 6.0.0.161 Beta 4 (Dec 19, 2007)

New in SecureCRT 6.0.0.140 Beta 2 (Dec 7, 2007)

New in SecureCRT 6.0.0.140 Beta 2 (Nov 27, 2007)

New in SecureCRT 6.0 Beta 1 (Nov 16, 2007)

Added support for sending a tabbed session to a new window and cloning a session in a new window. Sessions can also be dragged between SecureCRT windows.
Added an optional button bar that allows buttons to be mapped to strings, protocol functions, menu commands, scripts, etc. Different button bars can be created so that they can be used on a per session or per task basis.
Added support for launching external programs on the local machine through mapped keys and buttons on the button bar.
Added support for alpha transparency. The transparency can be set for the active and inactive windows. This allows viewing of items behind the SecureCRT window and the contents of two SecureCRT windows to be compared.
Added support for several Windows themes, which give the user interface a more modern appearance.
Added support for customizing the toolbar and menu by dragging and dropping items while in the Customize dialog.
Added a new default color scheme, "White / Black", which is a white foreground on a black background.
Enhanced portability by making a U3 installer available. Installing SecureCRT on a U3 drive makes it easier to use on any machine.
Added MSI installer support.
Added optional monthly pop-up dialog that offers to check for product updates.
Added support for locking sessions with a password while connected. While a session is locked, it cannot be typed in or closed.
Environment variables can be used in all paths specified in global and session options, which allows configuration files to be used by more than one person and makes it easier to move configuration files to other machines.
The autoreconnect prompt and countdown are now displayed in the session window instead of in a dialog. This allows connected sessions to be used while a disconnected session is trying to reconnect.
Added support for the Ymodem file transfer protocol.
Added "Connect to multiple sessions sequentially" to the TerminalAdvanced page in the Global Options dialog. When this option is set and multiple sessions are connecting, they will connect one after the other instead of at the same time.
Added a global option not to reuse disconnected tabs for connecting new sessions.
Extended the command-line options to support a username@hostname format.
Added new Session script object function LogUsingSessionOptions that uses the specified session's logging options.
Telnet: Added a session option to enable/disable NTLM authentication.
SSH2: Added a command-line option to specify the compression type(s).
The standard toolbar icons have been updated to use Windows Vista icons.
SecureCRT dialogs now use the font specified by the Windows display properties.
The line and character send delay settings, which were global settings, are now session-specific settings.
The scrollback buffer can be set to be up to 128,000 lines.
If the logging option "Append to file" is set and the session .INI file option "Log Multiple Sessions" is off, when one session is already logging to a file and another session tries to log to the same file, the user will be prompted for a different log file.
When recording a script, crt.Screen.Synchronous is set to true by default. This prevents data being lost by the script sending data too fast to be transmitted to the remote system.
If a script that does not exist is selected from the recently used script list, a prompt asking if it should be removed from the list is displayed.
The "Save password" check box is no longer shown on the "Enter Password" dialog when the "Auto Save Options" setting is off.
The global settings "Copy on Select" and "Paste on right button" are on by default. This only affects new installations.
Pressing the " " key on the numpad now produces a " " character in Linux and ANSI emulations.
Improved the error message that is displayed when attempting to give a session a name that is already being used.
Fixed: SecureCRT could crash when applying default session changes to all sessions.
Fixed: Files with Unicode names may not have been named correctly when transferred using Zmodem.
Fixed: Pasting into a SecureCRT session from an RDP session caused SecureCRT to hang.
Fixed: When using TrueType or ClearType fonts in a session, the right edge of some characters was cut off.
Fixed: If the session options "ANSI Color" and "Use Color Scheme" were enabled for the first tab, if a second tab was connected, the background color was not correct.
Fixed: The command-line option /POS did not override the session's initial position.
Fixed: If a relative path was specified for a custom menu that contained a script path and a log file that was in a different location than the script was used, the script could not be found.
Fixed: Xmodem transfers could fail when the remote machine sent a NAK. SecureCRT now handles the NAK.
Fixed: Unicode characters were not displayed correctly in the title bar.
Fixed: When the SecureCRT window was as tall as the monitor and then the chat window was shown, text in the session was obscured.
Fixed: Some menu item labels, such as Copy and About, could not be customized.
Fixed: DOS device names such as CON, NUL, PRN, COM1, COM2, etc. could be used as session names.
Fixed: SSH1/SSH2: When a password was specified in a URL session, it was not used.
Fixed: Telnet/SSL: Connecting to a server that was using a certificate with a large key size, could have resulted in the following error: "The buffers supplied to a function was too small".
Fixed: SFTP tab downloads failed if the file contained any characters that were illegal on the local file system (i.e., / : * ? " < > | ). SecureCRT now replaces any illegal characters with an underscore during the download.