PhilippC / PhilippC/keepass2android
[BUG] unlock with picture as keyfile no longer working on Samsung S23+
Nobody has claimed this yet.
- 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:
For years we've been using a 4MB picture to unlock our database. With latest release unlocking is no longer possible. K2A always reports that combined key is invalid. They keyfile is stored locally on a Samsung S23+. On windows unlocking with picture works perfectly fine. On Android with K2A it's broken.
Describe what you expected to happen:
Unlocking with our 4MB jpg file is working again. Currently we had to remove the keyfile by changing master key on windows to be able to use K2A.
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in Keepass2Android 1.14-r4 on Android 16 using a locally stored 4MB JPG keyfile on a Samsung S23+, then compare it with the same keyfile on Windows. Trace the unlock path that reports the combined key as invalid; done means the database unlocks with the picture keyfile again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- authentication, mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100