openid / openid/OpenID4VC-HAIP

Keys for DPoP should be attested to be highly secure

Open
#1 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

issuance
Dominant language
Makefile
Stars
57
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Let's make sure that keys we use for DPoP can be directly attested by the key attestation to be protected by the secure key store of the device (e.g. Secure Element, Secure Enclave etc.).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining how DPoP keys and key attestation are handled in this repository; the issue does not name files, tests, or entry points. Clarify the supported secure key stores and the attestation requirements before implementation, with completion defined as DPoP keys being verifiably protected by an approved device secure store.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.