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 versie 5.1 klaar staan met de volgende lijst van aanpassingen sinds de vorige vermelding in de meuktracker:
Bug fixes:SecureCRT 5.1 beta 4:
- In some cases, escape sequences beginning with "ESC ]" were incorrectly interpreted.
Changes:SecureCRT 5.1 beta 3:
- Added Global.ini option "Serialize Connections". If this option is set, when multiple sessions are connected at the same time, they are connected serially instead of in parallel.
- VCP/VSH: The command-line clients now display unsupported host-key algorithms as they are received from the server. Previously unsupported algorithms were displayed as blank strings.
- VCP/VSH: Entering the wrong passphrase for an SSH1 RSA public key no longer displays an "invalid structure" error. Users are now prompted to enter a passphrase until they use the correct one or cancel.
- If a generic proxy was misconfigured, it caused SecureCRT to hang, and disconnecting the session caused SecureCRT to crash.
- SecureCRT crashed when unsaving a password for a session and password that had been specified on the command line.
- The tab status indicator changed to "connected" when connecting to a host that did not exist if another tab that was connected was selected before the connection attempt timed out.
- SSH2: When editing the default session, it was possible do a password change.
- SSH2: Under certain circumstances, even though an X.509 host key had been accepted and saved, SecureCRT asked about accepting it during key re-exchange or when reconnecting.
- The installation program no longer removes old versions of SecureCRT from Windows Add/Remove Programs.
- For DNS addresses, SecureCRT uses the return list as is, rather than preferring IPv4 addresses.
- If SecureCRT and SecureFX were integrated, but were out of sync, it was possible for the authentication method and key exchange lists to be empty on the SSH2 page in the Session Options dialog.
- After installing SecureCRT for the first time, upon starting, the user was prompted to configure TAPI information and SecureCRT crashed if the dialog was cancelled.
- Under certain circumstances, printing did not work after upgrading from a version of SecureCRT prior to 5.0.
- If a log file name with parameter substitutions was specified and "Prompt for filename" was set, the log file name was not honored.
- In the Quick Connect dialog, changes made to the default session were only reflected for the default protocol.
- The transfer protocol name was modified in the session .ini file every time a connection attempt to that session was made.
- SSH1: Under certain circumstances, authentication failed when connecting to an SSH1 server using Quick Connect.
- SSH1: Entering the wrong passphrase for an SSH1 RSA public key resulted in an "invalid structure" error.
- SSH2: In the Local Port Forwarding Properties dialog, it was not possible to use the same local port as another port forward when the local IP address was different.