Make security key selection more flexible
維護者通常 2 天內回覆
@kpanuragh 已經在處理了。
開始於 2026年11月11日。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 55/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- linux, rust
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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.)
- 主要語言
- Rust
- 星號
- 310
- 分支
- 22
- 平均合併
- 1 天 15 小時
- 30 天內合併 PR
- 13
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
linux-credentials/credentialsd 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
linux-credentials/credentialsd#277 ·
維護者通常 2 天內回覆
-
documentation good first issue help wanted
難度 2/5 半天 新手友好度 62/100
linux-credentials/credentialsd#87 · 2 則留言 ·
維護者通常 2 天內回覆
-
`check_origin_from_privileged_client` drops browser signalling intermediate cross-origin iframes未關閉
難度 3/5 1-2 天 新手友好度 57/100
linux-credentials/credentialsd#276 ·
維護者通常 2 天內回覆
-
難度 3/5 1-2 天 新手友好度 52/100
linux-credentials/credentialsd#275 · 3 則留言 ·
維護者通常 2 天內回覆
-
Cancel request when client disconnects可能已有人在做 @kpanuragh 今天認領。 未關閉
難度 4/5 3-5 天 新手友好度 48/100
linux-credentials/credentialsd#274 ·
維護者通常 2 天內回覆
查看 linux-credentials/credentialsd 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 65/100
-
needs triage
難度 2/5 1-3 小時 新手友好度 76/100
pbakaus/impeccable#1620 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
swc-project/swc-next-issues#533 ·
-
bug
難度 2/5 1-3 小時 新手友好度 77/100
nautechsystems/nautilus_trader#5718 ·
維護者通常 1 天內回覆
-
`luvus --remote` cannot start on a host whose login shell is Nushell可能已有人在做 @schlich 今天認領。 未關閉status: needs triage
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 4 天內回覆