linux-credentials / linux-credentials/libwebauthn
Consider splitting PXP into a separate crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 579
- Forks
- 27
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 1
Description
PXP (formerly "hybrid", formerly "caBLE") now is being used as a transport protocol for multiple application protocols, including CTAP2 hybrid and the digital credentials API. We might want to split the transport-level handling into a separate crate that is consumed by libwebauthn, and perhaps a future Digital Credentials library.
The PXP specification has been broken out from CTAP 2.3, and an initial working draft has been published at https://fidoalliance.org/specs/hybrid/proximity-exchange-protocol-v1.0-wd-20260717.html.
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 reading the linked PXP working draft and locating the current PXP transport handling in libwebauthn. Determine which transport-level pieces could form a separate crate and how libwebauthn would consume them. Done means the crate boundary and migration scope are agreed, with the existing CTAP2 hybrid behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100