Feature Request: Support pre-computed clientDataHash (parity with Android/iOS APIs)
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
调研方向
从 xyz.iinuwa.credentials.xml 中的 D-Bus 接口定义以及 credentialsd 中的请求解析开始。然后检查 libwebauthn 的 register() 和 sign() 函数,以确定它们是否接受客户端数据哈希。完成的标准是选择并实现一种兼容的 API 形式,正确转发哈希,保留现有的 JSON 行为,并通过测试覆盖两条路径。
由索引模型根据 Issue 内容生成。
描述
Summary
Add support for accepting a pre-computed clientDataHash (SHA-256) as an alternative to clientDataJSON in the D-Bus API. This aligns with Android and iOS platform APIs, and enables a wider range of WebAuthn integration scenarios.
Background
The CTAP2 specification defines that authenticator operations (authenticatorMakeCredential and authenticatorGetAssertion) accept a hash of the client data, not the raw JSON:
hash (0x01): Hash of the serialized client data, provided by the client.
Reference: FIDO CTAP2 Specification §6.1
While browser-based WebAuthn flows typically construct clientDataJSON locally, there are several scenarios where the caller may already have the hash:
- Cross-device authentication (CTAP2 Hybrid/caBLE) - The initiating device may provide the hash directly
- Native application integrations - Apps may negotiate client data with their backend
- Remote desktop/VDI scenarios - The remote server constructs clientData and transmits only the hash
- Proxy/relay architectures - Intermediate systems may only forward the hash
Prior Art - Platform API Parity
Both Android and iOS platform APIs support this pattern:
Android (Credential Manager API)
val request = GetPublicKeyCredentialOption(
requestJson = "...",
clientDataHash = clientDataHashBytes // Optional pre-computed hash
)
Reference: Android Credential Manager Documentation
iOS (ASAuthorizationPublicKeyCredentialProvider)
let request = provider.createCredentialAssertionRequest(challenge: challenge)
request.clientDataHash = clientDataHash // Supports pre-computed hash
Reference: Apple Developer Documentation
Adding this support to credentialsd would bring Linux to feature parity with these platforms.
Proposed API Change
Add an optional client_data_hash parameter to the D-Bus methods:
Option A: New optional parameter (backward compatible)
<method name="MakeCredential">
<arg name="request_json" type="s" direction="in"/>
<arg name="client_data_hash" type="ay" direction="in"/> <!-- NEW: optional 32-byte SHA-256 -->
<arg name="response" type="a{sv}" direction="out"/>
</method>
Behavior:
- If
client_data_hashis provided (non-empty), use it directly - If
client_data_hashis empty, compute hash fromrequest_json.clientDataJSON(current behavior)
Option B: Separate methods
<method name="MakeCredentialWithHash">
<arg name="request_json" type="s" direction="in"/>
<arg name="client_data_hash" type="ay" direction="in"/>
<arg name="response" type="a{sv}" direction="out"/>
</method>
Use Case
This feature enables various integration scenarios where the caller has a pre-computed hash rather than raw JSON:
- Cross-device flows where another device initiated the WebAuthn ceremony
- Native applications with custom client data handling
- Remote desktop environments where authentication is redirected to the local machine
- Enterprise SSO integrations with proxy architectures
The key benefit is flexibility - allowing callers to provide either the raw JSON (current behavior) or a pre-computed hash when that's what they have available.
Security Considerations
This change maintains the same security model:
- The authenticator still requires user interaction (touch/PIN)
- The UI still displays the relying party information
- The cryptographic signature is still bound to the hash
The only difference is who computes the hash - the caller vs the credential service.
Implementation Notes
Looking at libwebauthn, the underlying register() and sign() functions may already work with the hash internally. The change would primarily be in:
- D-Bus interface definition (
xyz.iinuwa.credentials.xml) - Request parsing in
credentialsd - Passing the hash through to libwebauthn
Related
- W3C WebAuthn Level 3 §5.8.1 - client data hash computation
- FIDO CTAP2 Specification - authenticator protocol
- Android and iOS platform APIs (referenced above)
Questions
- Would you prefer Option A (optional parameter) or Option B (new method)?
- Are there any security considerations I might have missed?
- Is this something you're planning to implement, or would you be open to accepting a community contribution? I'd be happy to work on a PR if that would be helpful.
Thank you for considering this feature request!
- 主要语言
- 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 天内回复