PhilippC / PhilippC/keepass2android
[BUG] Database Password with Invalid char
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:
I update my database to v4 and now I can't open it with the following error:
"The input is nota valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters."
My password contains A-Z chars, a number and a underscore '_'
Describe what you expected to happen:
Expected to accept the password I always used, with the version 3 of the database
What version of Keepass2Android are you using?
1.10-pre
Which version of Android are you on?
14
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
Reproduce opening the v4 database in Keepass2Android 1.10-pre on Android 14 with a password containing an underscore, then trace where the invalid Base-64 error is raised. Compare the v3 and v4 password handling paths. Done means the existing password is accepted and a regression test covers this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- databases, mobile, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100