PhilippC / PhilippC/keepass2android
[BUG] database creation crashes with large keyfile (online only)
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:
BUG Keepass2Android version 1.14-r1 When creating a database using Drive (KP2A only) option when using a large 50MB keyfile it crashes during creation resulting in a corrupt header however a 33MB key works and NOTE a 50MB key works offline. Why is this crashing? How does KP2A handle the keyfile is it hashed in the header the same way as password? I read the wiki https://keepass.info/help/base/keys.html#keyfiles and found a 50MB keyfile would be hashed as I guessed. What function is used to hash large keyfiles because for cloud hosted I will need Argon2id.
Describe what you expected to happen:
I didn't expect it to crash
What version of Keepass2Android are you using?
1.14-r1
Which version of Android are you on?
13
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 database creation through the Drive (KP2A only) path on Android 13 with 33MB and 50MB keyfiles, then compare it with offline creation. Trace the keyfile hashing and online creation path; done means a 50MB keyfile creates a valid, reopenable database without crashing or corrupting the header.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- databases, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100