Skip to content

KiTTY 0.85.1.2-beta

Pre-release
Pre-release

Choose a tag to compare

View all tags
@hknet hknet released this 21 Aug 20:22
· 21 commits to kitty-0.85 since this release
kitty-0.85.1.2-beta
dfb1848

KiTTY 0.85.1.2-beta

A faster configuration window, the third run-on-connect fix, honest key protection, and a quieter kageant.

New:

  • KiTTYgen: "Add confirmation" button added. kageant asks before each use of a key whose comment carries the word "confirmation". The button appends it (and does nothing if a marker is there). Also fixed: after generating a key no control had the keyboard focus - Tab only beeped; the passphrase field takes the focus now.

Faster:

  • configuration window pre-builds its panels in the background. Panels are cached since 0.85.1.1; now the box quietly builds the not-yet-visited ones while it sits open, so by the time you click a category its panel already exists. Every switch - first visit or revisit - now costs about 40 ms (from 94 ms two releases ago).

Fixed:

  • The auto-command runs on every connect too. 0.85.1.1 made the scripting engine and the login script run again on reconnect, but Auto-command after login (Connection → Data) was the third sender with the same fault and was missed: it ran on the first connection and never again. (#36)

  • kageant and KiTTYgen warn when in-memory key protection is not working. SSH-2 private keys are normally held CryptProtectMemory-encrypted; when that API fails - which on a normal Windows it never does - the tools silently fell back to holding keys in plain memory. Now kageant shows a one-time warning and a permanent tray-tooltip line, KiTTYgen warns once, kittygen-cli warns on stderr. The check is a real protect/unprotect round trip, so a hooked or stripped crypt API is caught too. (SSH-1 keys were always held unprotected - the format is obsolete; KNOWN-ISSUES says so now.)

  • kageant never blocks itself with a message box you didn't ask for. A modal message box stops the agent from answering requests, so every ssh/git/scp call waits on it. The old-key-format warning could appear during the automatic key load at login - it is a self-dismissing notice there now. And a second kageant started with no arguments exits quietly instead of complaining "already running": upgrades and Windows' restart-apps machinery legitimately start one beside the autostart.

Upgrading: install over your existing version, nothing moves.

Full changelog & known limitations: https://github.com/hknet/KiTTY/blob/kitty-0.85.1.2-beta/KNOWN-ISSUES.md

Assets 6
Loading