When comparing KiTTY vs SSH of Windows' Linux subsystem, the Slant community recommends KiTTY for most people. In the question“What are the best SSH clients for Windows?” KiTTY is ranked 1st while SSH of Windows' Linux subsystem 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 Can store login credentials
Pro True Color support
Supports True Color, so software like Vim can display a really nice pallet.
Uses Unicode for the best character compatibility.
Pro It's extremely easy to get running
All you have to do is go to the Microsoft store, choose a Linux distro you like, and install the client for free.
Pro Full Linux shell
Uses all relevant Linux ssh commands as normal.
Pro Based on OpenSSH
OpenSSH is the reference for all ssh clients.
Pro Excellent way for Windows users to learn Linux
It is much easier and more convenient than dealing with a dual boot Linux installation.
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 Graphical problems
For example running Midnight commander (MC) makes terminal blinking.
Con Crontab and other background jobs don't work properly
Crontab only runs on ROOT, and it needs Windows to stay open. If you close it, you will kill the crontab. Some background jobs don't run on Windows WSL.
Con Does not install on PC virtual machines
Con Forces window to a certain size
Any other SSH client will render the remote server at whatever size the local client window is. The built-in SSH client on Windows, however, forces you to use a standard size, and it's small enough to cause problems.