Make security key selection more flexible

Abierto
#256 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@kpanuragh ya está trabajando en esto.

Desde el 11/11/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
linux, rust

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.)

Lenguaje dominante
Rust
Estrellas
310
Forks
22
Merge medio
1 d 15 h
PR fusionados (30 d)
13

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de linux-credentials/credentialsd

Todos los issues de linux-credentials/credentialsd

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.