Return basic authenticator information on connect

未关闭
#327 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
api

调研方向

Start from how getInfo responses are parsed and where authenticator metadata is stored, then look at the Device and Channel traits to see what is already exposed to clients. Decide which values (aaguid, minPinLength, maxPinLength) belong in the basic authenticator info and whether transports and preferredPlatformUvAttempts need abstraction first. Done means clients can read the agreed fields after connecting, with tests covering parsing and trait exposure.

由索引模型根据 Issue 内容生成。

描述

We should allow clients to get info about client devices when they are connected.

I don't think most of getInfo's values are useful to expose at this layer, but some that might be helpful for the UI:

  • aaguid (for looking up display name)
  • minPinLength (for example, to disable submit PIN button until the min pin length is met, prevents burning PIN attempts on a typo)
  • maxPinLength (to warn the user that it's too long when they type too much)

These are also useful, but might be better if we abstract over them in libwebauthn:

  • transports (for the platform to prefer smart-card over USB when possible, for post-quantum purposes)
  • preferredPlatformUvAttempts

Exposing those in the Device or Channel traits might be useful.

主要语言
Rust
星标
602
派生
33
平均合并
1 天 13 小时
30 天内合并 PR
9

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

linux-credentials/libwebauthn 的其他 Issue

查看 linux-credentials/libwebauthn 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。