PhilippC / PhilippC/keepass2android
YubiKey OTP via NFC to keepass2android ?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
On desktop I use KeePass 2.61 with OtpKeyProv plugin, and YubiKey generated tokens.
YubiKey also with keepass2aandroid 1.14-r4. Until recently (before Android update (OneUI 8 on Android 16) YubiKey tokens opened in keepass2android. [ok]
Now, they started opening in browser: https://demo.yubico.com/yk
Not sure, I suspect recent Android update made NFC behavior stricter, so apps can’t easily “steal” and block those links from opening.
I don't think user configuartion can resolve.
I think includeing related url as "supported link" in keepass2andoid could resolve ?
Thanks for your advice
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 YubiKey NFC token handling in keepass2android on OneUI 8 with Android 16, comparing it with the earlier behavior described. Read the app's NFC handling and supported-link configuration entry points, then determine whether the token opens in the app or the browser. Done means the intended YubiKey tokens open in keepass2android again without relying on user configuration.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100