Webauthn attestation should be an explicit choice

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

The payload names no source files, so start by finding where the Rust code builds the CTAP attestationFormats value and where the attestation preference from the relying party is read. The proposal is to default to ["none"], and to forward the requested formats only when the RP asks for direct attestation and the user has enabled a credentialsd-ui toggle that defaults to off. Done means the default path sends no attestation, and the toggle gates it. The design choice of the UI wording and the approach should be confirmed with maintainers before coding.

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

描述

Currently if the RP requests attestation and the authenticator supplies it, it's included in the response. Ideally this is something the client explicitly confirms they want. I suggest:

Always default to setting CTAP's attestationFormats = ["none"].

Only if the RP sets attestation = "direct":

  • Show a credentialsd-ui toggle to the user whether they want to include attestation that defaults to off
  • Only if the user enables it, forward the webauthn attestationFormats setting over CTAP.
主要语言
Rust
星标
310
派生
22
平均合并
1 天 15 小时
30 天内合并 PR
13

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

linux-credentials/credentialsd 的其他 Issue

查看 linux-credentials/credentialsd 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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