PhilippC / PhilippC/keepass2android
[BUG] Entries with expired date still offered for logins
Open
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:
If the valid date of an entry has been set to expired, the entry is still offered for logins.
Describe what you expected to happen:
Expired login data should not be offered for logins anymore.
What version of Keepass2Android are you using?
1.11-r0
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 the issue with Keepass2Android 1.11-r0 on Android 14 using an entry whose valid date is expired. Trace the login-offering flow and verify that expired entries are excluded. Done means expired login data is no longer offered while valid entries continue to be offered.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100