PhilippC / PhilippC/keepass2android

[BUG] Keyfile raises fail password

Open
#3,211 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
6.2k
Forks
478
Avg merge
1h 4m
Merged PRs (30d)
2

Description

Checks
  • I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:

Since yesterday, I cannot decrypt the kdbx file anymore on my Google Pixel 10 with Android 16. I'm using a Password with Keyfile.
I can open the file on my PC with password and the Keyfile. I have made a fresh copy of both files from my PC to the Phone, did not help. I also have tried other Keepass apps, it didn't work as well.
Then I changed the kdbx-database-file (on the PC) from password with Keyfile to password only and opened the new database. Now it works again.

Describe what you expected to happen:

I still want to use a Keyfile.
Is there a bug on Android 16 while calculating the decryption with a Keyfile?
Can you please check if there is a possibility for a workaround for Keepass2Android?
Thanks, Manfred

What version of Keepass2Android are you using?

1.14-r4

Which version of Android are you on?

16

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. Start by reproducing the failure on Android 16 with Keepass2Android 1.14-r4 using a KDBX file protected by a password and keyfile, then compare it with password-only decryption; done means keyfile-protected files decrypt successfully on the affected device.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp
Domain
mobile, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.