bpellin / keepassdroid Goto Github PK

Sometime in the past week or so, Android has broken my ability to use my KeePass database. I have a Drive shortcut to the file on my homescreen which would get the latest version of the file from Drive and then launch my KeePassDroid application. I used to just tap it, then KeePassDroid would launch, then I could enter my credentials and everything would work fine.

Now it just opens Drive and says 'file not supported'.

When I try to send/share the file, the Android share menu only shows me Inbox, Gmail, Beam, and Drive (and not KeePassDroid).

When I open KeePassDroid directly and select a file, Google Drive shows me the list of all files but they are all grayed out and I cannot select any of them.

When I download the file in drive (so now it's just in the 'downloads' directory on my phone), I still can't do anything with the file. When I try to use the share intent, it only shows me Inbox, Gmail, Beam, and Drive. Using the file picker from KeePassDroid also shows a gray filename and doesn't let me select it.

Anyone have any idea what happened here? I've been using this for years on many phones and I really love the app, but now it seems broken. Oddly, the list of recent files in KeePassDroid works (they are old Google Drive directories, pointing to older versions of my database). However, I assume those will eventually be garbage collected (and I can't get any new version of my database).

Any help/advice would be appreciated!

Cannot open database.

com.keepassdroid.stream.HashedBlock InputStream.read() returned value out of range -1..255: -117

I have had this setup where I pin my kdbx file in Google Drive and create a shortcut to it using the Google Drive Shortcut Widget. This way I could just tap the shortcut from my homescreen and it would open the database in KPD.

Now tapping Google Drive shortcut to database file gives "This file type is unsupported".

Selecting the file through OIFile Manager allows me to select file from /sdcard/Android/data/com.google.android.app.docs/files/pinned_docs_files_do_not_edit/" and type password, but when tapping OK i get: "Database format not recognized.".

However, if I download the file and tap it, it opens directly in KPD and everything works fine so I could just resort to manual syncing, but I would really appreciate if you could find out if it's a Google Drive issue or not.

Phone: Samsung Galaxy Alpha (SM-G850F)
Android version: 5.0.2
KeePassDroid version: 2.0.4
Drive version: 2.3.544.17.34

It'd be really nice if the design could be updated to material design. The current design is old looking and is what keeps people from using a proper open-source password manager.
A great UI should look good, work easy and still provide advanced options to advanded users. As a reference, the app 'openKeychain' is a perfect example of a great UI witb advanced options.
For Google's guide to material design checkout https://www.google.com/design/spec/material-design/introduction.html

Thanks!

Apart from storing in the external device storage, there are many suggestions about where to put them: internally, via FTP and via HTTP.

Google suggests that apps targeting newer Android versions should use the SAF to get data from data providers like local external storage and Google Drive. I don't know whether there are apps provides FTP and WebDAV access via this framework, though. Thank you for reading my suggestion. 😄

Hi,

When i attempt to add an entry without any group existing, it crashes, it would be nice to display a message to tell the user to add a new group before.

When setting cyrillic password to database, only length of password is checked.
Example: database pass "маша", all 4-letter pass are treated as ok: "петя"," окно","ядро"...

If you make a mistake while typing your password you have to manually delete the whole phrase (if you don't know where you have made a mistake).
is it possible to change the behaviour of the app to delete the written phrase if the password is wrong ?

I use MS OneDrive to sync my DB across my computers. I also have OneDrive on my Android phone and would like to open my database there.

When I open KeePassDroid and search for a database, it does try and open OneDrive, which is the only cloud storage app configured. I have tried setting it as an offline file, but that doesn't work.

The version in Google's Market claims to be 1.8.5.1, with a version code of 68.

There is no version code of 68 in the source code, it only goes up to 67.

On the google code downloads, 1.8.5.1 is version code 66, and 1.8.6 is 67.

(Copied from https://code.google.com/p/keepassdroid/issues/detail?id=205 )

It would be a great feature if KeePassDroid could import a keyfile for a database into its internal storage, so that no other application could gain access to it.

Initial discussion at https://groups.google.com/group/keepassdroid-discuss/browse_thread/thread/83583ddb851702e

"One of my concerns with using KeePassDroid is that even though I use a keyfile with my database, I am concerned about a rogue application having possible access to both my keyfile and database. Since the key file is loaded into sdcard space on the phone, any application can view it due to the permissionless FAT32 nature of the filesystem.

...

I don't mind as much that other applications can access encrypted database (which is on the system through Dropbox) as long as it requires two things that would be otherwise hard to get: my passphrase and keyfile. Putting the keyfile into internal storage would go a long way into ensuring my data is protected."

AFAICT, it is impossible to open an Keepass database I created on a desktop to use my yubikey OATH-HOTP configuration. It would be really nice if Keepassdroid would allow reading of a Yubikey NEO over NFC

Hi,

what do you think about FTP upload/download support of password database ?

Regards,
Stephane

I just tried loading my kdbx file, typed in my password and while loading it 'Forced close'ed. Logcat showed me (I'm typing this over, since I don't have usb atm):
java.lang.NullPointerException
at com.keepassdroid.database.load.ImporterV4.EndXmlElement(ImporterV4.java:670)
at com.keepassdroid.database.load.ImporterV4.ReadDocumentStreamed(ImporterV4.java:316)
...

I hope that is enough information to know what was happening. Thanks for the (already) great app ;).

Google introduced a new fingerprint authentification service with the release of the Nexus 5X and 6P called Nexus Imprint. Github user @afollestad created a library that wraps around the Google Api and provides fingerprint unlock with a passphrase fallback.
Would it be possible to implement this in Keepassdroid?

Library: https://github.com/afollestad/digitus

The password display function is almost useless because you use sans-serif font for display the password.

Where 0 and O are already hard to distinguish, the letters l and I are impossible to distinguish.

I can provide a screenshot if you want.

Please change the font style of the password display from sans-serif to monospace or at least provide a option to change the font-style or the font itself in the settings.

Would be great to have possibility to disable automatic "copy to clipboard", which is great function, but completely unnecessary for PIN numbers and other passwords used outside of the phone (like door codes etc).

Hello. Your app is vulnerable to clipboard catchers. Any app which needs to read clipboard can eavesdrop the credentials. The solution is to create a server and a client (addon in webbrowser) must connect to it, make mutual authentication and get info without using clipboard.

I've got a new smartphone, installed KeePassDroid and copied the database (My Codes.kdb) on the external card as done on the old smartphone.
I can open and read the database, but if I try to write & save a new item, I get the above mentioned error message.

Is it possible to add in support for KeePass databases that reside in cloud storage. example: keepassdroid database in Google Drive.

1. Current dark theme is hard to read on some devices. Could you implement light (black text on white background) theme as an altermative to current dark one? No need to implement any custom theme support or color tweaks: just a selector in settings with 2 variations (Light or Dark). Something like this (with additional color selector) is implemented in Total Commander.
2. Font size for login/password is small (at least on some devices). Could you add a setting for font size?

I have keepass on my Droid Turbo 2 and am unable to open a database.kdbx file that I copied over from my laptop. When I go to select the file, it just appears greyed out.

After the update to 2.0.5 I tried to open the database file and got "File not found". The file is synced by the Owncloud client and has special characters in its path.
/storage/emulated/0/owncloud/[email protected]%3A1111/ownCloud/keepass/kp2.kdbx

I've tried to replace @ with %40, didn't change anything. It went fine with 2.0.4.

I set a key file for my kdbx file, and tried to open it my phone (Android 4.2) and Xperia Z4 tablet (Android 5.0).
I could open it on my phone, but couldn't on my tablet.

In details, the key file is grayed out on the file chooser like this:

Any other file browsers (File Commander, OI File Manager, Ghost Commander) got the same result.

To reproduce:

1. Check Settings -> Application -> Save keyfile
2. Return to main screen, and pick a keyfile
3. Enter password to unlock keepass db
4. Exit KeePassDroid
5. Restart KeePassDroid

Expected: the path to the keepass key is filled in to the last key file selected
Actual result: the keepass key path is blank

This is for:
Android 2.2.1
Atrix 4G

I'll have a look and submit a patch if you will accept.

I just got a new Verizon BlackBerry Priv today. I installed and signed into Onedrive and Box and downloaded my .kdb file. I installed KeyPassDroid from the Play Store and am unable to open my .kdb file that I open all of the time on my Samsung tablets and multiple BlackBerry 10 phones without any problems.

When I browse to the file, it's grayed out and I can't select it. If I try to open the file from Downloads, Internal Storage (Documents or Downloads folder) or Onedrive or Box, the file either doesn't show or shows grayed out and I can't select it.

If I type the path/name in, it does work and if I use ES File Explorer to browse and find the file, that works also.

The version of KeyPassDroid I'm using on the Priv is 2.0.4.

Open kdb with any password on Russian coinciding count of characters.
Step to reproduce:

1. Create kdb
2. Input password and re-password for kdb some pass in RU locale ex. 'пароль'
3. Open kdb and input password any in RU locale with same count of characters ex. 'вывыпр'
4. Profit
   This is a serious security hole

Install Android N developer preview. Launch Keepass. Upon unlocking I see the following error.

com.keepassdroid.stream.HashedBlockInputStream.read() returned value out of range -1..255: -117

Database does not open.

Hi,

If i open up Keepassdroid on my x86 Tablet with ICS 4.3 it crashes after typing in my Password. I attached some hopefully helpful output from catlog.

04-09 10:23:02.361 D/dalvikvm(5231): Trying to load lib /data/data/com.android.keepass/lib/libfinal-key.so 0xa066df20
04-09 10:23:02.361 D/dalvikvm(5231): Added shared lib /data/data/com.android.keepass/lib/libfinal-key.so 0xa066df20
04-09 10:23:02.361 F/libc (5231): Fatal signal 11 (SIGSEGV) at 0x010001a0 (code=1)
04-09 10:23:02.561 I/DEBUG (1571): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-09 10:23:02.561 I/DEBUG (1571): Build fingerprint: 'generic_x86/wetab/wetab:4.0.3/IML74K/eng.corvus.20120315.155503:eng/test-keys'
04-09 10:23:02.561 I/DEBUG (1571): pid: 5231, tid: 5273 >>> com.android.keepass <<<
04-09 10:23:02.561 I/DEBUG (1571): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 010001a0
04-09 10:23:02.561 I/DEBUG (1571): eax f9faff0d ebx 01000004 ecx 00000010 edx 00000000
04-09 10:23:02.561 I/DEBUG (1571): esi a066d960 edi 000000ba
04-09 10:23:02.561 I/DEBUG (1571): xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
04-09 10:23:02.561 I/DEBUG (1571): eip 9af1cfc8 ebp 5bde595b esp 9b0307c0 flags 00010246
04-09 10:23:02.711 I/DEBUG (1571): #00 eip: 9af1cfc8 /data/data/com.android.keepass/lib/libfinal-key.so (aes_encrypt_key256)
04-09 10:23:02.711 I/DEBUG (1571): #1 eip: ffffffff (aes_encrypt_key256)
04-09 10:23:02.711 I/DEBUG (1571): #2 eip: ffffffff (aes_encrypt_key256)
04-09 10:23:02.711 I/DEBUG (1571): #3 eip: ffffffff (aes_encrypt_key256)
04-09 10:23:02.711 I/DEBUG (1571): #4 eip: ffffffff (aes_encrypt_key256)
04-09 10:23:02.711 I/DEBUG (1571): #5 eip: ffffffff (aes_encrypt_key256)
04-09 10:23:02.711 I/DEBUG (1571): #6 eip: ffffffff (aes_encrypt_key256)
04-09 10:23:02.711 I/DEBUG (1571): #7 eip: ffffffff (aes_encrypt_key256)
04-09 10:23:02.711 I/DEBUG (1571): stack:
04-09 10:23:04.731 I/BootReceiver(1630): Copying /data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)
04-09 10:23:04.741 W/InputDispatcher(1630): channel 'a0b244a0 com.android.keepass/com.keepassdroid.fileselect.FileSelectActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
04-09 10:23:04.741 E/InputDispatcher(1630): channel 'a0b244a0 com.android.keepass/com.keepassdroid.fileselect.FileSelectActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
04-09 10:23:04.741 D/Zygote (1573): Process 5231 terminated by signal (11)
04-09 10:23:04.761 D/dalvikvm(1630): GC_FOR_ALLOC freed 1660K, 21% free 11427K/14407K, paused 25ms
04-09 10:23:04.761 I/WindowManager(1630): WIN DEATH: Window{a0a4c868 com.android.keepass/com.keepassdroid.PasswordActivity paused=false}
04-09 10:23:04.761 I/ActivityManager(1630): Process com.android.keepass (pid 5231) has died.
04-09 10:23:04.761 W/ActivityManager(1630): Force removing ActivityRecord{a0a86e28 com.android.keepass/com.keepassdroid.PasswordActivity}: app died, no saved state
04-09 10:23:04.771 W/InputDispatcher(1630): Attempted to unregister already unregistered input channel 'a0b244a0 com.android.keepass/com.keepassdroid.fileselect.FileSelectActivity (server)'
04-09 10:23:04.771 E/InputDispatcher(1630): Received spurious receive callback for unknown input channel. fd=264, events=0x8
04-09 10:23:04.771 W/InputDispatcher(1630): channel 'a0a6f078 In Bearbeitung… (server)' ~ Consumer closed input channel or an error occurred. events=0x8
04-09 10:23:04.771 E/InputDispatcher(1630): channel 'a0a6f078 In Bearbeitung… (server)' ~ Channel is unrecoverably broken and will be disposed!
04-09 10:23:04.771 W/InputDispatcher(1630): Attempted to unregister already unregistered input channel 'a0a6f078 In Bearbeitung… (server)'
04-09 10:23:04.771 I/WindowManager(1630): WINDOW DIED Window{a0b244a0 com.android.keepass/com.keepassdroid.fileselect.FileSelectActivity paused=false}
04-09 10:23:04.771 W/WindowManager(1630): Failed looking up window
04-09 10:23:04.771 W/WindowManager(1630): java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@a0a92970 does not exist
04-09 10:23:04.771 W/WindowManager(1630): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7156)
04-09 10:23:04.771 W/WindowManager(1630): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7147)
04-09 10:23:04.771 W/WindowManager(1630): at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1529)
04-09 10:23:04.771 W/WindowManager(1630): at android.os.BinderProxy.sendDeathNotice(Binder.java:417)
04-09 10:23:04.771 W/WindowManager(1630): at dalvik.system.NativeStart.run(Native Method)
04-09 10:23:04.771 I/WindowManager(1630): WIN DEATH: null
04-09 10:23:04.771 I/WindowManager(1630): WIN DEATH: Window{a0a6f078 In Bearbeitung… paused=false}
04-09 10:23:04.771 I/WindowManager(1630): WINDOW DIED Window{a0a6f078 In Bearbeitung… paused=false}
04-09 10:23:04.791 I/ActivityManager(1630): Start proc com.android.keepass for activity com.android.keepass/com.keepassdroid.fileselect.FileSelectActivity: pid=5278 uid=10102 gids={1015}
04-09 10:23:04.801 I/dalvikvm(5278): Turning on JNI app bug workarounds for target SDK version 10...

Keepassdroid update from a couple days ago now prevents me from using the app at all. Upon opening all I get is "unfortunately keepass droid has stopped". :( Any way to troubleshoot? Have been using the program successfully for the past year or so. Database file is synced via dropbox. I see some people are having issues with GDrive, so possibly another cloudsync issue or something?

Just updated the app and can't open my kdbx any more, local or gdrive I always get a Bad file descriptor error

Because of security I keep my database in file with extension that not .kbdx. KeePassDroid can not open it. But Keepass2Android can do it.

The language switch button is inactive on the stock screen keyboard (HTC sense input). HTC One M8, Lollipop, stock.

I had the battery drain issue that was reported over at Google Code. When I checked the battery use view, the top item was Android OS with what seemed like a high CPU total, but since it has never happened before and I just installed KeePassDroid today, I'm pretty sure it's the culprit.

The one thing I can think of that might be different from a default install is that I set the database lock option to "never." Could this mean that it keeps the file open somehow? I've changed it back, and will see if the problem reoccurs.

Can't update app
"KeePassDroid" can't be updated. Try again, and if the problem continues, get help troubleshooting. (Error code: 907)
It does continue. I havent been able to update.

It'd be nice to be able to use keyfiles located on NFC tags (as NDEF text records) instead of files located on the device itself.

I'd like to edit also the expirity date of an entry, as I can using the desktop KeePassX application. It is useful when adding/editing eg. credit cards. Can you please implement also this feature?

In the desktop client one can autofill the username and password. The android app uses the clipboard, which is rather insecure.
As of android 5.0 it is possible for apps to enter text directly which would be more practical and more secure.

It'd be nice if you added the above QR code to the website and the readme.

it is awesome app, requires least permissions too . Thanks

I request that the GUI be changed to Material design based .

It would be nice if keepassdroid would be able to read and write the new database format of keepassx 2.0. Currently, KeepassX 2.0 has to convert the DB to its new format which doesn't allow me to copy it to my android device.

hi,

my KeePass database has a General and a Backup group when I open it.
I'm using KeePassX at home and KeePass Portable at work with no particular modifications/options set. I don't know which program creates/updates the Backup group but it must be either of the two mentioned.
I assume that others have the "Backup" too.

The ability to hide it by option would be great OR even better to simply start in the General group as "root"

The version beforehand stated, how to build the src-files with the android-ndk. However since the latest update you cannot execute android-ndk from the keepassdroid-root-directory.
Executing it from the "/app/src/main/jni"-directory does stuff, but doesn't build the source, as far as I can gather it.

So either the readme needs to be updated, or there are is a Android.mk files missing in the root-folder?

After installing latest update which is actually a downgrade to 2.0.4 Keepassdroid no longer opens.

I have tried restarting phone and uninstalling and reinstalling keepassdroid. App still fails to open.

Running android 5 on Samsung SM-N9005

The app description on Google Play currently contains the statement "Please report issues at http://code.google.com/p/keepassdroid/issues/list so I can follow up". This should be updated to the GitHub location, since the former is well into the process of being shut down.

Even if option is activated in preference. I need to click display password at each start.

Suggestion: Can you use the digital fingerprint to open the database instead of entering password? It will be very usefull. It's available on Galaxy S7.

Hi

I've got two phones, a Nexus 6 and a Nexus 5x, both with 6.0.1 March 1, 2016 security level.

On the Nexus 6 I've got keepassandroid v2.04 released March 8.
On the Nexus 5x I still have 2.05, that was briefly released before being dropped to 2.04 (I've not updated it yet)

On the Nexus 6, v2.04 I can't open any files kdbx files from either Google drive or my download folder.
I've cleared cache, uninstall/ install and problem remains.

On the Nexus 5x with v2.05 I don't have problems with the same scenario.

This is identical of the issue previously reported and that people said it was fixed on the 8th March version. However I noticed that they mentioned using Android 5.0

I'm wondering if this is specific to Android 6.0?

If you need any logs and let me know how to do it, I'll be willing to help.

I use this program a lot and it's excellent.. Keep up the awesome work!

Jose

I upgraded my Nexus 5 to Android 6 yesterday and I noticed that the icons in the notification bar are not correctly displayed; only two plain white squares are shown instead.

If you swipe down to see the full notification list, the icons are shown, though a little different.
I'll try to attach two screenshots to this issue.

Just a minor convenience.

Hello I use a .kdb database which is hosted on Google Drive. It remains in grey when I want to open it. Same if I choose "available offline". It worked before the Google Update.What can I do to read my kdb file on Android?