VanDyke Software heeft versie 7.3.3 van SecureCRT uitgebracht. SecureCRT is, simpel gezegd, een uitgebreide versie van Putty. Iets minder simpel gesteld is het een client voor remote control, file transfers en datatunneling met behulp van ssh. Ssh is een methode om een beveiligde verbinding tussen twee computers op te zetten, waarbij zowel de data als een deel van het ip-verkeer worden versleuteld. SecureCRT is beschikbaar voor Windows, Linux en OS X, en de prijs van een licentie begint bij honderd dollar. Sinds versie 3.2.1 zijn de volgende veranderingen en verbeteringen aangebracht:
Changes in SecureCRT 7.3.3New features:
- Previous versions of SecureCRT supported saving passwords and other sensitive data. In order to improve the security of this feature, SecureCRT now requires a passphrase to be created the first time version 7.3.3 runs. This passphrase will be used to encrypt and decrypt sensitive data stored in the session database, such as passwords and send/expect logon scripts.
- SecureCRT hung if logon actions were being edited for multiple sessions and one of the strings being replaced was blank.
- The crash reporter dialog, which reports crashes for previous runs of SecureCRT, was being displayed after the SecureCRT window was displayed, which caused confusion about when the crash had occurred.
- SSH1: If the "Auto reconnect" global option was set and a session that did not have the username and/or password saved got disconnected, if the user did not respond to the username or password prompts, multiple prompts were displayed until SecureCRT eventually crashed.
Changes in SecureCRT 7.3.2Changes:
- The escape sequence ESC E (DECNEL, next line) is treated like a CR (or CRLF) so that the command on that line gets logged.
- SSH2: When attempting to authenticate using a CAPI key or certificate with a smart card, if the card returns an error, SecureCRT attempts to continue authentication, which allows authentication to succeed with certain smart cards, such as GoldKey.
- SecureCRT crashed when attempting to run a Perl script using ActiveState ActivePerl 5.18 and 5.20. SecureCRT still cannot run the script. Switching ActivePerl 5.16 is recommended.
- When the global option "Save window state for each session" was set and SecureCRT was in full-screen mode, if a local shell session was opened or a session was cloned, SecureCRT went out of full-screen mode.
- If autohide was on for the session manager, the most recently opened session was not selected when the session manager was shown again.
- If a keymap was modified through a script, it was not always reloaded.
- When using the Connect dialog, if a session with saved credentials was connected by double clicking, extraneous text appeared in the session window before the prompt.
- Telnet: When connected to a session with a character or line send delay specified, the delay was not honored when a script sent a string.
- Windows: On Windows 8.1, SecureCRT crashed if TAPI was selected as the protocol in the Quick Connect dialog and the Configure button was pressed.
- Mac/Linux: If a local shell session was started from an alias, it was not possible to interrupt output using CTRL+C.
- Mac/Linux: If the global option "Show horizontal scroll bar" was set and the connected session had the session options "Show horizontal scroll bar" and "Synchronize view to size" set, after performing a long directory list that filled the screen, the last row had extra space below it.
- Mac/Linux: The crash reporter dialog did not show crash information for the most recent crash.
- Linux: The background color of the space to the right of the tabbed sessions in the tab bar was the background color of the default session's color scheme instead of the background color of the tabs.
- Linux: The global INI-file-only option "Toolbar Style" was not honored if it was set to a value other than 2.