KeePass DX is an Android password manager implemented from Keepass password manager.
KeePass DX was created to meet the security and usability needs of a KeePass application on Android :
- To be easy to use with secure password management and form filling tools.
- To use only tools under open source license to guarantee the security of the application (With open source store and no closed API).
- To be in a native langage (java) for weight, security and a better integration of the application.
- To respect Android design, architecture and ergonomic.
- We do not recover your sensitive data on a private server or a closed cloud, you have control of your passwords.
- We respect KeePass file standards to maintain compatibility and data porting on different devices (computers and portable devices with different operating system).
- The code is open source, which implies increased security, you can check how the encryption algorithms are implemented.
- We remain attentive to your needs and we can even integrate the features that you have defined.
- We do not put advertising even in the free version.
- We allow users to save and use passwords, keys and digital identities in a secure way by integrating the last encryption algorithms and Android architecture standards.
- You can increase the security of your database by increasing the rounds of encryption keys. (In Settings -> Database Settings when your database is open) Warning: Increase the number of rounds sparingly to have a reasonable opening time.
Yes this is possible. Otherwise, we recommend using cloud with personal server and open source license, like NextCloud to be sure how your databases are stored.
Yes you can, but you must first save the .kdb or .kdbx file from your database to an external storage (like a hardrive or a cloud). We recommend you save your data after each modification so incase you loose your android device you could retrieve the data and import it into the new KeePass DX installed on the new android device.
- PlayStore only needs an APK generated and manually signed to be available on the store, it usually takes 20 minutes to be available because it is deployed with fastlane. But the management of the APK and its data by the google servers is obscure.
- F-Droid, to ensure that the code is open source, checks the sources directly on git repository (by checking the presence of new tags) and builds itself the APK that the server signs during the compilation of code and dependencies. Updating the project will take 1-10 days for F-Droid to analyze all available repositories, build sources and deploy the generated APK. So F-Droid is slower for deployment but it is run by volunteers and guaranteed a clean APK. :)
The offline and online client concepts only exists with Keepass2Android because the file access network tools are directly integrated into the code of the main application. Which is a very dubious choice knowing that it is not normally the purpose of a password management application to take care of external file synchronization on clouds (which can be under closed licensed and recover your data base), it is rather the purpose of the file management application.
Yes, we have integrated a secure openning option of fingerprint for android devices that support this feature, so no one can access the application without scanning his/her fingerprint or fill a master key.
No, you can not open a database file without the master password (and / or) the associated key file. Be sure to remember your master password and save the key file in a safe place.
Yes, we welcome this you could go ahead and do that on our github: https://github.com/Kunzisoft/KeePassDX