When comparing KiTTY vs SecureCRT, the Slant community recommends KiTTY for most people. In the question“What are the best SSH clients for Windows?” KiTTY is ranked 1st while SecureCRT is ranked 6th. The most important reason people chose KiTTY is:
- Sessions filter - Shortcuts for pre-defined command - The session launcher - Automatic logon script - URL hyperlinks - Running a locally saved script on a remote session - Send to tray - Transparency - Quick start of a duplicate session - SSH Handler: Internet Explorer integration - pscp.exe and WinSCP integration - New command-line options
Ranked in these QuestionsQuestion Ranking
Pro Includes additional features over PuTTy
- Sessions filter
- Shortcuts for pre-defined command
- The session launcher
- Automatic logon script
- URL hyperlinks
- Running a locally saved script on a remote session
- Send to tray
- Quick start of a duplicate session
- SSH Handler: Internet Explorer integration
- pscp.exe and WinSCP integration
- New command-line options
Pro Startup sessions
Support start-up sessions which allow you to specify the window/tab layout, working directories, and programs to run on startup.
Pro Source Code Available
Source code is available so you could modify or review changes.
Pro True Color support
Supports True Color, so software like Vim can display a really nice pallet.
Pro Can store login credentials
Ability to store passwords/passphrases locally.
Pro Background image
Ability to overlay the terminal background with an image.
Pro Auto login script
Automatic processing of commands after conncetion was made.
Uses Unicode for the best character compatibility.
Pro Scriptable via Python API
Has a Python API to control most aspects of the terminal and sessions. Scripts can be bound to buttons, menu items, and keyboard shortcuts.
Pro Buttons Bar
SecureCRT while not free has the ability to make common commands in to button for faster command processing. Commands like: exit, clear, :wq!, ls -lha and the etc.
Pro Puts emphasis on security
SecureCRT has strong data encryption and secure authentication through the support of password and public keys.
Con No centralized configuration
Each session holds its own configuration of all features. This means that if one wants to change a configuration common to all sessions (say, the terminal font), it has to be changed in each stored session separately.
A better solution would be to have a default configuration and store only the changed elements for each session (both configurations would be merged, with e priority on the specific one).
Con No tabbed sessions.
No built in support for tabbed sessions. Requires an add on.
Con Not free
Paid product. Some nice additional Cygwin type features and server version are integrated, but for most users the feature set probably does add enough value for a paid only client.