Feature Request: Support pre-computed clientDataHash (parity with Android/iOS APIs)
Mantenedores costumam responder em até 2 dias
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 45/100
Direção de pesquisa
Comece pela definição da interface D-Bus em xyz.iinuwa.credentials.xml e pelo parsing das requisições em credentialsd. Em seguida, inspecione as funções register() e sign() de libwebauthn para determinar se elas aceitam um hash dos dados do cliente. O trabalho estará concluído quando uma forma de API compatível for escolhida e implementada, o hash for encaminhado corretamente, o comportamento JSON existente for preservado e ambos os caminhos forem cobertos por testes.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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!
- Linguagem predominante
- Rust
- Estrelas
- 310
- Forks
- 22
- Merge médio
- 1d 15h
- PRs com merge (30d)
- 13
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de linux-credentials/credentialsd
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
linux-credentials/credentialsd#277 ·
Mantenedores costumam responder em até 2 dias
-
Update screenshotsAbertadocumentation good first issue help wanted
Dificuldade 2/5 Meio dia Facilidade para iniciantes 62/100
linux-credentials/credentialsd#87 · 2 comentários ·
Mantenedores costumam responder em até 2 dias
-
`check_origin_from_privileged_client` drops browser signalling intermediate cross-origin iframesAberta
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 57/100
linux-credentials/credentialsd#276 ·
Mantenedores costumam responder em até 2 dias
-
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 52/100
linux-credentials/credentialsd#275 · 3 comentários ·
Mantenedores costumam responder em até 2 dias
-
Cancel request when client disconnectsTalvez já em andamento @kpanuragh assumiu hoje. Aberta
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 48/100
linux-credentials/credentialsd#274 ·
Mantenedores costumam responder em até 2 dias
Todas as issues de linux-credentials/credentialsd
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
-
needs triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
pbakaus/impeccable#1620 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
swc-project/swc-next-issues#533 ·
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
nautechsystems/nautilus_trader#5718 ·
Mantenedores costumam responder em até 1 dia
-
`luvus --remote` cannot start on a host whose login shell is NushellTalvez já em andamento @schlich assumiu hoje. Abertastatus: needs triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 4 dias