In Keepass2Android, this is the default setting. It therefore makes sense to ensure that changes to the KeePass database are automatically saved. In practice, this can mean that you lose changes if you edit the same entry on both devices before the databases are synced. Because KeePass has a similar feature, you can, in theory, use the KeePass database from two different devices simultaneously. Before Keepass2Android saves the database to the cloud, it first checks if the database has been modified and, if it detects changes, it asks if you want to merge the two databases. This can cause syncing problems if you changed the KeePass database under Windows. If you want to open the latest KeePass database in KeePassDroid, you first have to navigate to the database file in the cloud drive app.Īnother difference is that Keepass2Android automatically uploads changes in the database to the cloud drive. If not, Keepass2Android will get the database from its cache. Of course, this is only possible if you are online. How is this different from just opening the database from your cloud drive app with KeePassDroid? The main point here is that Keepass2Android will always get the latest version of the database from the cloud when you open the app. Merge KeePass databaseĪfter you give Keepass2Android access to your cloud drive, you can browse your folders for the KeePass database. This feature isn’t available for the other cloud drives. You can restrict the password safe app to just one folder on your Dropbox where you store your KeePass database. Keepass2Android has a nice feature that can ease your queasiness a little. The app might contain vulnerabilities that another app could exploit. It is not just that you have to trust the developer of the app. I always feel somewhat queasy when I allow an Android app to access Dropbox. In this case, you might prefer Keepass2Android Offline, which doesn’t support cloud syncing. Of course, you can also store database files locally on your phone. In addition, you can load the KeePass database from a third-party Android app. Keepass2Android supports Dropbox, OneDrive, Google Drive, SFTP (SSH file transfer), FTP, HTTP (WebDav), and HTTPS (WebDav). I recently moved to Keepass2Android, mostly because it allows me to sync the KeePass database with my cloud drive more conveniently. I have been using KeePassDroid, the most popular KeePass-compatible Android app (according to the Google Play statistics), for quite a while. This doesn’t completely eliminate the risk because KeePass could contain security holes that an attacker might be able to exploit, but you have to draw the line that separates security awareness from paranoia somewhere. If someone manages to download your KeePass database from your cloud drive, he would still need the key file from the second cloud drive and your master password. Another option, one that Keepass2Android supports, is to store the key file on a second cloud drive on which you (I hope) use another password. Of course, this only makes sense if you don’t store the key file on your cloud drive you have to copy it manually to your phone. Another is to use a key file for your KeePass database. You can take a few security measures to help you remedy the risk.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |