Make security key selection more flexible

Aberta
#256 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

@kpanuragh já está trabalhando nisso.

Desde 11/11/2026.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
55/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
linux, rust

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Rust
Estrelas
310
Forks
22
Merge médio
1d 15h
PRs com merge (30d)
13

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de linux-credentials/credentialsd

Todas as issues de linux-credentials/credentialsd

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.