SecureCrt for mac

SecureCRT(R) 8.3.3 (Official) -- May 3, 2018 Copyright (C) 1995-2018 VanDyke Software, Inc. All rights reserved. This file contains the SecureCRT product history. It includes lists of new features, changes, and bug fixes sorted by release. For a product description, installation notes, registration information, and contact information, please refer to SecureCRT_README.txt (downloaded with this installation). Changes in SecureCRT 8.3.3 (Official) -- May 3, 2018 ---------------------------------------------------- New features: - Added a global option to disable all printing. - ssh-add can be used to add keys from a remote Linux, Unix, or Mac system to SecureCRT's agent using agent forwarding. Change: - Mac: The accelerator for resetting the zoom level to 100% was changed to COMMAND+SHIFT+0. Bug fixes: - SecureCRT crashed when the remote system tried to write to the VT320 status line, but the VT320 status line had not been enabled by the remote. - SecureCRT did not send FIN when disconnecting Telnet sessions. - If the SecureCRT window was maximized and then minimized and restored, when a session was connected, the window was restored instead of remaining maximized. - The hostname was not remembered if the protocol was changed from SSH2 to Telnet when the Connect bar was used to connect to a remote system. - In Python scripts, the Session object method "Unlock" did not work. - Windows: On Windows 10, if RDP was used to connect to a machine running SecureCRT with a session connected and then RDP was disconnected, SecureCRT crashed. - Mac: If focus was in the Connect bar and text was entered causing the auto complete dropdown to be displayed, SecureCRT crashed if it was closed using the red "X". - Mac: If the user didn't have write permission to the /cores file, a warning was displayed when SecureCRT started. - Mac: Keymapping did not work correctly when a key was mapped to COMMAND+X. - Mac: In the Color Scheme dialog, the scrollbar thumb became unresponsive when it was dragged to scroll the ANSI colors list. - Mac: In a Python script that created a message box with "Yes" and "No" buttons, the default button could not be set to "No". - Linux: On Ubuntu, after selecting a session in the Session Manager or Connect dialog, it could take a long time to connect the session or display the session's properties. Changes in SecureCRT 8.3.2 (Official) -- February 8, 2018 --------------------------------------------------------- Bug fixes: - SecureCRT crashed when ALT+<number> was pressed and no sessions were open. - When using Quick Connect, if a firewall that was just created was specified, the firewall was not used when the session connected. - Extracting a public-key file from a private key failed with ECDSA keys that were created with ssh-keygen. - When a session contained output and was scrolled back half way, if ALT+<left click> was used to do a column select, the selection would not scroll beyond the visible terminal area even though there was output below. - Windows: If a session had the global option "Show connection closed dialog" set and the "Close on disconnect" session option was set, typing "exit" in the session caused SecureCRT to crash. - Windows: Tapping the scroll bar or scroll bar arrows caused the session output to scroll two pages instead of one. - Windows: In the Command window, CTRL+A did not do a Select All. - Linux: On Ubuntu 16, the mouse cursor was very small. Changes in SecureCRT 8.3.1 (Official) -- December 7, 2017 --------------------------------------------------------- Changes: - Added default key mappings to Xterm emulation for CTRL+HOME, CTRL+END, CTRL+SHIFT+END, CTRL+SHIFT+HOME, SHIFT+HOME, SHIFT+END, SHIFT+PGUP, and SHIFT+PGDN. - Linux: Added the ability to map CTRL+TAB to a key. Bug fixes: - SecureCRT crashed if the pre-defined color scheme "Solarized Light" was deleted. - If a dialog was displayed while attempting to open a log file when connecting to a session and the session attempted to automatically reconnect before the dialog was dismissed, SecureCRT crashed when the dialog was dismissed. - The performance of scrolling large amounts of data with keyword highlighting and the "Minimize drawing" option set was significantly slower than in version 8.1. - In the multi-line paste dialog, the clipboard text was very small on high-DPI monitors. - Windows: SecureCRT could not be installed on Windows Server 2008. - Windows: If the Connect bar was moved to the menu bar using the Customize dialog, auto complete in the Connect bar no longer worked. - Windows: Many dialogs had display issues on high-DPI monitors when the system was scaled to 125% or 175%. - Windows: The keymap editor dialog had some alignment issues on high-DPI monitors when the system was scaled to 111%. - Mac/Linux: When SecureCRT was in tiled mode, if a Python script requested the Tab Object property Index, the value returned was not correct. - Linux: On Ubuntu 16, the mouse pointer was very small on high-DPI monitors. Changes in SecureCRT 8.3 (Official) -- November 9, 2017 ------------------------------------------------------- No changes. Changes in SecureCRT 8.3 (Beta 4) -- November 2, 2017 ----------------------------------------------------- Bug fixes: - SecureCRT could crash if a script was attempting to connect to a Serial session in one window while another window was attempting to connect to a Serial session and both were using the same serial port. - If a button in the Button bar was mapped to run a script or launch an application that was not located in the SecureCRT install folder, after SecureCRT closed and restarted, the script or application field was blank. - Forward slashes specified in the Arguments field in a Button bar button that launched an application were converted to backslashes. - When Find was used to search for text in a session and the Find dialog was left open, if the screen and scrollback were cleared, attempting to find text using the Find dialog did not work. - When options that should take effect immediately were changed in the Default session and applied to all sessions, the changes were not honored until a reconnect occurred. - The script method Config.Save() could not be used to overwrite existing sessions. - When SecureCRT and SecureFX were integrated and the "Cache session password" option was on, if quick connect was used to connect to an SSH2 host that used password authentication and then SecureFX was launched, automatically connecting to the same SSH2 host, the password had to be re-entered. - Windows: SecureCRT could crash when the computer woke from Sleep or Hibernate mode. - Mac: SecureCRT crashed if the Find dialog was open and the session tab that was active when it was opened went away while the Close button in the Find dialog was being clicked. - Mac: If COMMAND+ENTER was mapped to Mapping Disable, the application still went into full-screen mode when COMMAND+ENTER was pressed. - Mac: Switching between tabs could be slow when there was no default printer. - Mac: Specifying a Korean log file name by selecting "Log Session" from the file name resulted in a corrupted log file name. - Mac: If SHIFT+ENTER was pressed in the Session Manager, pressing ENTER to connect a session no longer worked until SecureCRT was restarted. - Mac: After connecting and disconnecting a session, if a session was connected using the Connect bar, focus remained in Connect bar. - Linux: On high-DPI monitors, text and fields in some dialogs were cut off. Changes in SecureCRT 8.3 (Beta 3) -- Oct