Replies

Well . . . that kind of meets the definition of crippled, doesn’t it? Or are you saying the paid version is also read-only?

Up until write support was added, the paid version was read only. The free version currently has more features than the paid version for the previous 2 years

To be clear, the lite version came about as a result of write support being added to the paid version. Thus, the lite version isn’t crippled, but the paid version is enhanced

I use KeePass on both PC and Android. AFAIK, there are only three real choices of android apps that are compatible with KeePass PC databases: KeePassDroid, Keepass2Android, and KeepShare.

I know nothing about KeepShare other than it costs money. (There is a crippled, “Lite” version, but why bother with crippled when the other two are free and work quite well?)

…

To clarify on KeepShare, since you don’t know anything about it: it adds usability and features that KeePassDroid and Keepass2Android both lack. Namely, a secure PIN unlock mechanism, and auto-fill. Yes, AUTO-FILL.

Auto-fill of usernames and passwords works across all apps, chrome and the built-in web browser (for those of you not using chrome, but no other browser support).

The Lite version is crippled? No, it’s read-only. It does everything else the paid version does. KeepShare, like the other two is also fully open source. If you wanted to not pay, you can build it yourself. I’m not stopping you. On top of this, nothing’s stopping you from using KeePassDroid and/or Keepass2Android for all your writing needs; I’ve just put a lot more effort and thought into how the UI should work vis-a-vis the others. Most people don’t even want write support.

PIN unlock is also secure as it is used in a form of 2FA. In order to unlock the database, you must have access to your Google Drive for some app-private data, and the PIN. Neither one individually can unlock your passwords.

Oh, and a random bit of trivia, KeepShare isn’t my only security-related piece of software (nor is it my only KeePass-related). I am also the creator of chromeIPass and passIFox for those that use it (although I neglect those pretty badly).