Upgrading and migrating

Normal upgrades

Install the new version over the old one. Saved connections, groups, pinned host keys and settings are kept. Close the app first — an installer cannot replace a running executable.

The app also checks for updates itself and can download and apply one. That path refuses plain HTTP and any host that is not cysectek.com, and verifies the package’s SHA-256 before applying it.

Coming from before 0.7.0

0.7.0 introduced the mandatory app password. On first launch after upgrading you will be asked to set one, and any passwords you already had — which were protected by Windows DPAPI — are re-encrypted onto the new key straight away. You do not need to re-enter them.

Read first launch before you choose that password. It cannot be recovered.

Session transcripts also changed in 0.7.0: they are encrypted and named .clog. Older plain-text logs are left alone. If you have any, they contain exactly the sort of thing that made encrypting them necessary — worth reviewing and deleting.

Coming from before 0.7.1

0.7.1 fixed key exchange against equipment offering ecdh-sha2-nistp256 or the SHA-1 exchanges — most enterprise network hardware and all older kit. If a device previously failed with “No common key exchange algorithm”, it should now connect. Nothing needs migrating.

Uninstalling

Through Settings → Apps, as normal. This removes the application. Your saved connections, host keys and transcripts are in your user profile and are not deleted by the uninstaller — delete that folder too if you want the machine clean.