A new version of KiTTY Portable has been released. KiTTY is a fork of the popular PuTTY telnet and SSH client with additional features packaged as a portable app, so you can connect in to your systems on the go. It's packaged in PortableApps.com Format so it can easily integrate with the PortableApps.com Platform. And it's open source and completely free.
Update automatically or install from the portable app store in the PortableApps.com Platform.
Features
KiTTY is a lightweight telnet and SSH client for Windows, along with an xterm terminal emulator. It allows you to securely connect to your systems while on the go. KiTTY also features a sessions filter, command shortcuts, transparency, and other additional features. Learn more about KiTTY...
PortableApps.com Installer / PortableApps.com Format
KiTTY Portable is packaged in a PortableApps.com Installer so it will automatically detect an existing PortableApps.com installation when your drive is plugged in. It supports upgrades by installing right over an existing copy, preserving all settings. And it's in PortableApps.com Format, so it automatically works with the PortableApps.com Platform including the Menu and Backup Utility.
Download
KiTTY Portable is available for immediate download from the KiTTY Portable homepage. Get it today!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Comments
missing Default%20Settings in KiTTY Portable 0.72.0.3
When reinstalling KiTTY Portable 0.72.0.1 or 0.72.0.3
missing in path ..\PortableApps\KiTTYPortable\Data\Sessions\..
the file Default%20Settings
Thanks for the heads up. This
Thanks for the heads up. This seems to be base app related. kitty_portable.exe from the original github repo crashes when used standalone, too. When placing an existing Sessions folder containing Default%20Settings alongside, it starts without error. I'll use that as a workaround for a Rev 2.
-edit-
I sent out a Revision 2 package with a workaorund to fix that issue. Cyd (the developer of the base app) is aware of the issue (55) as well and has a fix that would be included in the next release. Maybe we better just wait for that than tinker with the app structure.