ISSUE 1: Your private key *should* be password protected. But this app *requires* that you save the passphrase *with* the private key (if you leave the passphrase blank, the connection never succeeds). That is poor security practice.

What should happen is that you should be required to enter the passphrase for the private key when you first try to use it, then the app should remember it for the session only. It should *never* save the passphrase or the unencrypted private key (which it is doing right now).

ISSUE 2: If you create a new key in the Key Manager, then select it and choose “Email”, a mail dialog appears. At that point, your bluetooth keyboard gets disabled! (you need to hit the “+” button and choose an email from your contacts).

Instructions for creating longer private keys:If you want to create longer keys, you can’t do it inside the app. And since the app only supports des3 for key encryption, you need to use openssl rather than ssh-keygen. The following command will do it: