Managing credentials

Everything to do with the app password is on the Security page inside the app.

Changing it

Enter the current password and the new one. Every stored credential is re-encrypted onto the new key as part of the change, so nothing needs re-entering. This is worth doing if you ever typed the password somewhere it might have been logged.

Locking

Lock now closes the vault immediately; the app asks for the password again before it will decrypt anything. There is also an idle lock — lock after a stretch of no keyboard or mouse activity — which is off by default and worth turning on for a laptop that travels.

If you forget it

The saved credentials are gone. Not recoverable, not by us, not by anyone. This is what “the password is never stored” means in practice, and it is the same property that makes a copied credential file useless to an attacker.

You can set a new password and carry on. The entries themselves — hosts, ports, usernames, groups — survive; it is the stored passwords that cannot be read. Re-enter them as you use each device.

What is stored where

• SSH, SFTP passwords and key passphrases — encrypted in the app’s own store.
• Private keys — not stored at all. Only the path to the file.
• RDP passwords — handed to the Windows client through the Credential Manager at launch, because that is the only way to give mstsc a password without putting it on a command line.