linux-credentials / linux-credentials/credentialsd
Enumerate available transports
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 259
- Forks
- 19
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 12
Description
Right now, available transports are just hard-coded in the credential service ([here](https://github.com/linux-credentials/linux-webauthn-platform-api/blob/32b042a4e10af808efdeb8f241f9896ed55ef442/xyz-iinuwa-credential-manager-portal-gtk/src/credential_service/mod.rs#L53-L76)). We should change this to query the system for available USB and Bluetooth controllers to determine which transports we should make display to the user for selection.
(Eventually, this will also need to include linked hybrid devices, but for now, let's focus on the hardware enumeration.)
Contributor guide
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 with xyz-iinuwa-credential-manager-portal-gtk/src/credential_service/mod.rs at the linked transport list. Investigate how the system exposes USB and Bluetooth controllers, then make the displayed transport choices reflect the hardware found; done means available controllers determine the selectable transports, while linked hybrid devices remain out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- authentication, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100