Make security key selection more flexible

Offen
#256 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

@kpanuragh arbeitet bereits daran.

Seit 11.11.2026.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
55/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
linux, rust

Rechercherichtung

Read the existing Enter PIN and credential selection flows to see how ceremony input is received, then trace how USB devices are discovered and how device information is represented. The issue proposes tracking available devices on the ceremony and selecting one by ID, with optional automatic selection. Done means supporting physical, virtual, and automatic selection while exposing device names for display; the issue does not name specific files or tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

In response to feedback from the GNOME Design team, we need some more flexibility for different ways of selecting a security key:

  • physical: allow a user to touch a USB security key to select it
  • virtual: allow a user to view the connected USB security keys and click a button in the menu to start using it.
  • automatic: if a single USB security key is plugged in, then automatically start the ceremony on it.

Currently, we only support the first (physical). I think the latter two can be achieved by syncing a list of available devices to the backend, and then add a function on the frontend to select one of these devices by ID. That covers the virtual one. To achieve the automatic selection, the backend can choose, for example:

  • if no devices are connected at the start of the ceremony, and exactly one arrives, automatically select it
  • if exactly one device is present at the beginning of the ceremony, wait 1 second, then automatically select it.

This allows credentialsd not to mandate a specific pattern for selecting devices, and desktop environments can decide what's best for their users.

I think this means a few things:

  • We need a way to identify USB devices when they are plugged in. This can be as simple as an index
  • We need to query authenticator info for the name of the model for display purposes.
    • This might mean we'd need to cache the output of getInfo in the device struct.
  • We need to make devices a property of the ceremony that can be monitored for changes.

We have a pattern for receiving user input in the Enter PIN and credential selection flows. We can copy that for this input.

We may also want to consider updating our polling API to allow streaming in updates to the device list instead of polling, which would be more efficient and easier to track a stable list. (This is also a consideration for NFC, so I'll post this as a separate issue.)

Vorherrschende Sprache
Rust
Sterne
310
Forks
22
Ø Merge
1 T. 15 Std.
Gemergte PRs (30 T.)
13

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus linux-credentials/credentialsd

Alle Issues in linux-credentials/credentialsd

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.