I suggest you ...

Support .jpg file as key file with KeePass 1.24 database

Does KeePassDroid support the use of non-generated (i.e., existing) key files?

I locked my KeePass v1.24 .kdb file with both a password and a key file, opting for an existing .jpg as the key file rather than generating a new one.

After I got the two files file onto my Android device independently (.kdb via DropBox, and .jpg via Google Drive), KeePassDroid keeps giving me the message, "Invalid password or key file".

However, the same password and key file work in KeePass 1.24.

1 vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    dmmiller2k shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • dmmiller2k commented  ·   ·  Flag as inappropriate

        Further notes: I tried the password+key file scenario using a key file generated by KeePass 1.24, and KeePassDroid still couldn't open the database (with the correct password and key file). Nor did it work with the key-file-only scenario (with either key file type: existing or generated).

        (I still haven't tried generating a key file with KeePassDroid and seeing whether that works with KeePass itself, but I am not enamored with the dependency on my Android device).

      Feedback and Knowledge Base