SecureCRT is een client voor remote control, file-transfer en data-tunneling met behulp van SSH. Dit is een methode om een beveiligde verbinding op te zetten tussen twee computers. Hier wordt dan zowel de data als een deel van het IP-verkeer versleuteld met een encryptie methode. VanDyke Software heeft sinds kort een nieuwe bčtaversie klaar staan met 5.0 beta 6 als de versieaanduiding. Het changelog ziet er als volgt uit:
- Added the session name to disconnect/reconnect messages.
- Improved handling of mismatched DLLs when SecureCRT and SecureFX are integrated.
- SSH1: Added support for TIS authentication.
- SSH2: Added new compatibility mode for Tectia using SHA1 hash with X.509 RSA certificates.
- SecureCRT sometimes took a long time to start or did not start at all.
- Using ALT+
to navigate to a disconnected tab caused the status icon to change to connected.
- The default keymap did not include the ALT+
- SecureCRT sometimes displayed extra characters when Linux emulation and the Terminal font were used.
- Line-drawing characters were not printed correctly although they were displayed correctly.
- When SecureCRT could not load the default printer settings, it was not possible to exit the Printing pages in the Global and Session Options dialogs.
- Under certain circumstances, Find highlighted an extra character.
- Typing an exit command in an SFTP tab during a transfer caused SecureCRT to crash.
- Pressing CTRL plus any key during a Zmodem transfer interrupted the transfer.
- SecureCRT crashed when attempting to exit the application during a Zmodem transfer.
- When the global option "Save window state for each session" was enabled and SecureCRT was started using a shortcut that was set to run minimized, the SecureCRT window did not start minimized.
- Copying a session to a different folder failed if that session name already existed in the folder.
- The menu item File\Print\Selection was sometimes available when nothing was selected.
- SecureCRT crashed when a key was mapped to clone the tab and that key was pressed, but cloning was not allowed for that session.
- License errors were reported as "317 and 317".
- When SecureCRT and SecureFX were integrated and a session was saved using the Quick Connect dialog, a protocol did not get set for the other application.
- It was not possible to integrate SecureCRT 5.0 and SecureFX 3.0 on machines if they had never been installed.
- When SecureCRT and SecureFX were integrated, sometimes the icons displayed in the File Types page in the Global Options dialog were incorrect.
- Serial: SecureCRT crashed when data was attempted to be sent after the session sending data had been closed.
- TAPI: SecureCRT crashed when attempting to connect to a TAPI session and no modem was present.
- SSH: Because the SSH1 and SSH2 key exchange algorithms settings were incorrectly being shared, SecureCRT could report "no compatible key exchange method" when attempting to connect.
- SSH: SSH URLs did not working correctly.
- SSH: The View Host Key dialog did not scroll when the host key did not fit.
- SSH1: Modified the identity string to be the same as 4.1. which was what some devices expected.
- SSH1: SecureCRT disconnected during Zmodem downloads and reported the error "Invalid packet header".
- SSH2: In some cases, X11 forwarding was very slow.
- SSH2: SecureCRT hung if certificate authentication was selected, but there were no certificates in the CAPI store.
- SSH2: Could not use the GSSAPI key exchange method when connecting to an IP address and other key exchange methods were also allowed.
- SSH2: Attempting to use an invalid public key caused SecureCRT to crash.
- SSH2: The system function SHGetFolderPathA was being imported incorrectly, which caused problems on Windows 98.
- VSH: Attempting to commit large modified binary files in CVS caused VSH to hang.