-
-
Notifications
You must be signed in to change notification settings - Fork 276
Lightweight password manager for Android, KeePassDX allows editing encrypted data in a single file in KeePass format and fill in the forms in a secure way.
KeePassDX was created to meet the security and usability needs of having a KeePass app on Android:
- Easy secure password management and form filling tools.
- Only libre software tools to strengthen the security of the app.
- No closed APIs, or open APIs linked to closed tools.
- Native langage (Kotlin, Java, C) for a small app size, security and a better integration.
- Android design, architecture and ergonomics.
- Your data is stored in a single encrypted file that you manage, it is not stored on a private server or in a closed cloud. You have control of your passwords.
- KeePass file standards are used to maintain compatibility and portability with different devices (computers and portable devices with different operating systems).
- The code is open source, meaning you can check how the encryption algorithms are implemented.
- The developers are attentive to your needs, and can even integrate the features you define.
- No advertising. Not even in the free version.
No, you can not open a database file without the master password (and/or) the associated keyfile.
Be sure to remember your master password and save the keyfile in a safe place. To prevent this from happening, you could use some of the methods for remembering passphrases described in the Create and maintain secure passwords guide (securityinabox.org).
Yes, there is an alternative fingerprint/device credential opening option for Android devices that support this feature, so no one can access the app without scanning your fingerprint or enter your master key.
You must always know your master password, the advanced unlocking is only a faster unlocking tool.
Users are allowed to save and use passwords, keys and digital identities in a secure way by integrating the latest encryption algorithms and Android architecture standards. All the source-code can be used, studied, changed, and distributed freely.
You can increase the security of your database by changing the encryption algorithm and increase the rounds of encryption keys. (In Settings → Database Settings when your database is open)
Warning: Increase the number of rounds sparingly to maintain a reasonable opening time.
The application will be deleted from your phone, but your database (stored in a .kdbx file) will remain.
You can open this file at any time in the future if you install KeePassDX again. For the same reason, if you wish to remove all traces of using KeePassDX, you need to delete both the application and the database file.
Hopefully you made a backup beforehand. Make sure you haven't simply forgotten where you stored the file in the first place. Search your phone for a file with a .kdbx extension.
Yes, but you must save the .kdb or .kdbx file from your database to external storage first (like a hard-drive or to a secure cloud). It is recommended to backup your data after each modification in case you lose your Android device. That way you can retrieve the data and import it into a new installation of KeePass DX on your new Android device.
You've probably opened your database in read-only mode. You can change the opening mode on the password selection page with the pencil icon. It's also possible that your file manager provides a read-only file URI, in which case please refer to the documentation for the file manager you're using.
Yes, you will need to copy the password database file to another phone or to a computer, install a KeePass compatible program on your computer or new device and then you will be ready to open the database.
Make sure that you copy the file over secure means, like your own trusted USB disk or connecting the phone directly to the computer. Assess if the other phone or computer is a secure environment to open your password database on.
It's always a question of balancing security and usability. We therefore recommend that you increase your encryption settings sparingly, so that you can open your database quickly, depending on your device. If you want the best security, put all the numbers to the maximum but you will not be able to open your database either because it will take way too long.
Your phone may be much less powerful than your PC, so when you set a decryption time of one second on your PC, it may take much longer on your phone. The solution is to lower the unlock time by lowering the KDF in the database security settings.
Yes, but it's important to note a few details to ensure security.
Make sure you share the username and password through a secure channel. The best option would be to exchange account details in person or in encrpyted communication. Once this is done, you can keep these account details in their own KeePassDX databases.
It is also possible to create a password database file (.kdbx) with shared accounts, and exchange it over secure channels (e.g. USB memory stick) as well as the master password. Once you work with a shared database file, you should assign a person in charge of managing the database file, including backups, and update if any changes happened to any shared accounts.
In certain circumstances, you may consider an online password manager. It is important that you understand the risks involved and take appropriate measures, such as excluding highly-sensitive accounts from the online database. There are open source alternatives.
The offline and online client concepts only exists in other apps because the file access network tools are directly integrated into the code of the main app. It’s a different choice that doesn’t meet app design and safety standards considering it is not normally the purpose of an Android password editor app to take care of external file synchronization on clouds (which can be under closed licensed and recover your database), it is rather the purpose of the file manager app.
Of course, you use the file manager you want, whether it is connected to internet or not.
Note that it is planned to create a separate file manager app to handle file sharing requests over the network.
Yes, You can of course add the cloud app of your choice to your file manager. We recommend using a cloud with a personal server and AGPLv3+ license. You can find a non-exhaustive list of compatible file managers on the wiki.
KeepassDX uses the file managers on your device. If your default manager is not connected to your cloud, you need to open your cloud app and select your database file. The linked file provided by the content provider may have a strange name, the alias feature can be used for better visibility.
KeePassDX uses one of your device's file manager and stores the generated links in the "recent databases" list. If the selected file manager breaks the link, it is necessary to re-open the file from your manager because it does not have the functionality to keep the persistent links. (More info on this in File Manager and Sync)
Yes, you can upload and download your attached files, there is even an internal image file viewer. But your attached files should not be very large. For large files, use alternative open source data encryption solutions (virtual encrypted disks).
The code for the database is constantly optimized (by ordering the nodes, managing the compression, and using the adapted version of the base). The filesize will be smaller, but all data will be present.
KeePassDX has protections against TapJacking, so that other applications that use overlays cannot recover keystrokes and steal your passwords. Make sure you don't have any applications that override the KeePassDX UI. The "Smart pixels" setting can cause this behavior. https://developer.android.com/reference/android/view/View#security
If Settings → Form filling → Magikeyboard settings → Entry selection and Settings → Form filling → Magikeyboard settings → Timeout are both enabled, the opening an entry will load it into magikeyboard and begin the magikeyboard timeout for clearing the entry.
Once the magikeyboard timeout has elapsed, the database will be locked, which may happen sooner than the main app timeout set in Settings -> App settings -> Timeout.
The same behavior can occur if you use clipboard notifications, have clipboard timeout enabled and copy your first item from the notification.
KeePassDX is protected against TapJacking, so if an app covers KeePassDX but leaves transparency, you think you're pressing buttons when you're not. You need to deactivate the app causing the overlay in your device settings "Display over other apps".
The Android framework will not allow the DexModeReceiver broadcast receiver to run unless KeePassDX is successfully launched once outside of DeX mode. After that, it will work inside Samsung DeX without any problem.
There are various strategies which you could implement :
- It is possible to give a password database misleading name which would suggest it is something else like "notes.odt" or "image.png". You can instruct KeePassDX not to remember which database it opened last time. Open
Settings -> App -> App setting -> Historyand deselect optionsRemember database locationsandShow recent files. You will need to remember yourself which file is saved where to access your password database. And you will need to open it directly from KeePassDX. - You can hide the applications name and icon or simply add a credential to prevent its access using a custom android launcher.
Yes, It is currently possible to unlock a database using your Yubikey. This feature is supported starting from version 3.5.0.
KeePassDX allows its users to test new releases in advance on the Play Store beta channel. This beta channel is used to test new KeePassDX features that will be implemented later in production. It is not recommended to use your normal database on this channel. Even if the code is audited at each release, there may be unexpected bugs (and that's why this channel exists). All the feedbacks of bugs of this channel are obviously taken into account and corrected for a future release of the final version.
- the Play Store only needs an APK to be generated and manually signed to be added, it usually takes a few hours to be available because it is deployed with Fastlane. The management of the APK and its data by the Google servers is obscure.
- On F-Droid, to ensure the code is libre, it checks the sources of the Git repository directly (by checking the presence of new tags). Then an APK is built that the server signs during the compilation of the code and dependencies. Updating the project takes 1-5 days for F-Droid to analyze all available repositories, build sources and deploy the generated APK. So F-Droid is slower for deployment, but is run by volunteers and guaranteed to be a clean APK. :)
All versions currently have the same usage features.
- The Libre version is the version provided by F-Droid, it is guaranteed to have no proprietary code, and is not linked to any closed services. The app is automatically signed and compiled from the GitHub repository. It is possible to unlock the themes with a procedure.
- The Free version, for everyday use, is the basic version at the Google Play Store. It is compiled and signed by the developers, and sent to the Play Store to be cataloged by Google.
IzzyDroid retrieves the Free compiled version in addition to the Libre version, which may be ahead of schedule. You can migrate data from one version to the other using the backup procedure.
KeePassDX Pro is the unlocked version of KeePassDX with unlocking cosmetic content and non-standard protocol features, but more importantly, it is available to assist development.
The contributions are necessary because the project requires a lot of work and maintenance and few human resources are dedicated to it.
The Pro version is accessible after having purchased Contributor Pro app (both applications must be installed on the same device) or after another contribution (you will receive by e-mail a procedure to unlock the Libre version of F-Droid).
For former KeePassDX Pro users, it is possible to transfer the properties of a KeePassDX application to another version (more info here)
Instead of directly providing these optional visual styles, they are an incentive to contribute and replace advertising without depriving users of functionality in the free version.
Non-standard protocols used in computing prevent interoperability with other applications. Proprietary and non-standard formats therefore do not respect the computing freedoms of free and open source software, and requires more integration work for no added value.
The Steam TOTP algorithm is not a standardized protocol and is therefore not a standard feature. Manual selection of this algorithm can therefore only be unlocked after a contribution.
The procedure to unlock these themes in KeePass Libre is sent by e-mail manually so feel free to ask at [email protected] if you have made a contribution.
Yes, do so on GitHub: https://github.com/Kunzisoft/KeePassDX/issues