SecureCRT is a GUI-based SSH / Telnet client and a terminal emulator that features support for a wide array of protocols such as SSH, TAPI, serial and rlogin. Its list of capabilities includes secure transfers, highly configurable sessions and SSH encryption, to name the most important ones.
Even though it quickly became a popular choice among network administrators, SecureCRT is often criticized for its selling price. While development and networking companies are able to afford this cost, day-to-day users are less likely to spend as much on a Telnet client, especially that free emulators are available.
Such an application is PuTTY, considered to be one of SecureCRT’s fiercest competitors. Although PuTTY is free, SecureCRT has a great deal of advantages, one of them being the higher level of security, which makes the comparison unnecessary, in our opinion.
SecureCRT features the most accessible user interface that we’ve seen in a terminal emulator, allowing you to create and customize up to five thousand tabbed sessions. In addition, the application facilitates encrypted logons and provides flexible authentication options.
Repetitive tasks can be processed via scripting languages such as VBScript, PerlScript, Python and Jscript. SecureCRT also bundles a script recorder, which makes it easier to automate routines.
File transfers can be achieved via the integration with SecureFX. The sessions can be shared between these two applications, thus enabling the possibility to run FTP, SFTP and SCP transfers without the need to re-enter passwords.
In conclusion, SecureCRT is definitely worth your while. Compared to similar products, it’s very comfortable to work with, it features extensive protocol support, it encrypts the data using a wide array of ciphers (AES, Twofish, Blowfish, 3DES and RC4) and it allows you to use WSH scripting engines in order to automate tasks. Considering all of its capabilities, we find that SecureCRT’s price is fair.
Limitations:
· 30-day trial
· Nag screen
What's New in This Release:
Bug fixes:
· SecureCRT hung if a script called Screen.CurrentColumn or Screen.CurrentRow before user authentication had completed.
· If a button was given a label that included an ampersand (&), the ampersand was not shown correctly on the button.
· If a button bar was given a name that contained an ampersand (&), the ampersand was dropped.
· Windows: SecureCRT could take a long time to start if there were a large number of autostart sessions and the tab status indicator option was set to "Background colors".
· Windows: If a button bar other than "Default" was selected in the default session, that setting was not honored.