There are some more "expert" features like use of One-Time-Passwords (entered via NFC with a Yubikey NEO, ) or support for Keepass 2's placeholder system (). Since the initial release, I have added quite a bunch of further features: A custom keyboard can be used to enter credentials (because clipboard is unsafe in Android) for users of the PC version there is an option to synchronize the database through WebDAV, FTP, SFTP, Dropbox, OneDrive or GoogleDrive. That's much better than entering the strong, long master password each time. To protect the database in case a user loses his phone, a short password must be entered to unlock the database. ![]() the master password is never stored on SD card). I decided to publish it anyway because it already had a few more features - including full compatibility with Keepass 2, browser integration or QuickUnlock: QuickUnlock is a technique to keep the database in memory (i.e. When my app was nearly finished, Keepassdroid added write support (at least in beta mode) as well. InfoQ: What makes Keepass2Android different from other password managers? I decided to do this by porting the app to C# with Mono for Android to use the original Keepass 2 code for modifying the password databases. So I started to think about adding that feature on my own. (It was originally created for use with Keepass 1 which it can also write, but that didn't help me.) As I started to use my phone more and more, I wanted to create accounts and store the passwords from the phone as well. Unfortunately, it only provided read-only access to my database. I had Keepassdroid on my phone to access my passwords there as well. Keepass 2 is a great password manager which I was using since quite a while. ![]() ![]() InfoQ: Can you explain what problem Keepass2Android was created to solve? Besides its features as a password store, this project is a good case study for combining Java and C# in a single Android application. ![]() In this interview we talk to open source developer Philipp Crocoll about Keepass2Android.
0 Comments
Leave a Reply. |