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. Voor meer informatie en een overzicht van alle mogelijkheden verwijzen we jullie door naar deze pagina. VanDyke Software heeft de eerste bètaversie van SecureCRT 5.2 uitgebracht met de volgende veranderingen:
SecureCRT® 5.2 (beta 1) enhances tab functionality with the ability to open new sessions in tabs, new scripting capabilities, and tab tooltips. Use the CTRL+TAB option to switch to the most recently used tab, and automate processes by using scripts to connect tabs, connect SFTP tabs, clone tabs, activate tabs, and close tabs.
- Added support for unauthenticated and basic HTTP proxies.
- Added script functions to support working with tabs. These functions allow scripts to connect tabs, connect SFTP tabs, clone tabs, activate tabs, and close tabs.
- Added a /T command-line option that supports launching sessions in tabs. This flag can be used with /S and with sessions that are not in the session database, such as URLs.
- Added a global option to have CTRL+TAB switch to the most recently used tab.
- Tab control displays tooltips (or hover text) to show the full tab label.
- Added support for Telnet over SSL.
- Added a global option to paste on right mouse click.
- Added a global option to display the elapsed time for connected sessions in the status bar.
- Added a session option to translate incoming CRs to CRLF.
- Added a session option to map ANSI line drawing characters to "+", "|", etc. when they are copied to the clipboard.
- Added a global INI-file only option "ZModem Force All Caps Filenames to Lower Case on Upload", which specifies whether or not all caps filenames should be converted to lowercase during a Zmodem upload.
- SSH2: Enhanced X.509 host-key support by validating X.509 host-key certificates.
- SSH1/SSH2: Added /ACCEPTHOSTKEYS command-line parameter to SecureCRT, which causes host keys to be automatically accepted.
- Removed the command-line clients VSH, VCP, VSFTP, VPKA, and VKEYGEN from the installer. These clients will be available as a separate package.
- Added a global and session printing option to force black on white printing.
- SecureCRT handles
] R in Linux terminal mode.
- If an HTTP proxy was being used and the session was disconnected before the hostname was resolved, CPU usage went up to 100%.
- Changing a session's protocol from Telnet to SSH2 did not change the port number like it did in SecureCRT 5.0 and prior versions.
- The "Color Schemes.ini" file could get corrupted when multiple instances of SecureCRT were launched.
- If display changes were made, such as showing or hiding the tab bar or chat window, the window size was incorrect when subsequent session windows were launched.
- If SecureFX was integrated with SecureCRT and the SecureFX path specified in the Global.ini file pointed to a 2.x version or an invalid path, the error "Show Terminal Only session while running SecureFX" was displayed.
- When editing the default session and a tab other than the first tab was active, the "Apply change to all sessions?" prompt was displayed even if no changes were made.
- When Midnight Commander was running and the session was using Xterm emulation, clicking the mouse beyond the 80th column generated garbage.
- SecureCRT was inaccessible if it was minimized from a script when a dialog, such as the Connect dialog, was being displayed.
- Cancelling a script did not report the line number where the script was cancelled like it did in versions prior to 5.0.
- Fixed the following tests in vttest that SecureCRT had been failing.
- Line-drawing tests in "Test of double-sized characters" set.
- Request terminal parameters test in "Test of terminal reports" set.
- Scrolling region and column mode escape sequence test in "Test of known bugs" set.
- Upgrading to a newer version of SecureCRT did not remove the old entry in Add/Remove programs.
- SSH2: SecureCRT could not validate the server's x.509 DSA host key when the key was not encoded using ASN.1 (F-Secure and SSH Communications servers).
- SSH2: SecureCRT could not validate the server's X.509 RSA host key if the server used the SHA-1 hash (later versions of F-Secure and SSH Communications servers).
- SSH2: If an incorrect username was entered in the username prompt dialog and the "Save username" check box was unchecked, this check box was incorrectly checked when re-prompting for the username.
- SFTP: SecureCRT crashed when using tab to complete a filename in an SFTP tab.