PhilippC / PhilippC/keepass2android
[FEAT] Nitrokey Support
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
KeePassXC now supports Nitrokey 3 as a Challenge-Response method. However, a database locked with a Nitrokey cannot be unlocked with Keepass2Android.
When selecting "Password + Challenge-Response for Keepass XC" as the master key type, Keepass2Android looks for a YubiKey, and does not detect the Nitrokey.
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 tracing the master-key handling for "Password + Challenge-Response for Keepass XC" and the existing YubiKey detection path. Determine how Nitrokey 3 support should fit alongside YubiKey support; done means a Nitrokey-locked database can be unlocked in Keepass2Android without breaking the existing YubiKey flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- authentication, mobile, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100