Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add security consideration: Extending a type doesn't imply authorization to issue the type #302

Open
danielfett opened this issue Mar 18, 2025 · 0 comments

Comments

@danielfett
Copy link
Member

Example:

  • there's a european PID type "urn:ec.eu.x.y.z" and a national type "urn:de.bla" that extends "urn:ec.eu.x.y.z"
  • a rogue issuer issues a credential "urn:attacker" that extends either "urn:ec.eu.x.y.z" or "urn:ec.eu.x.y.z"
  • it is now important that verifiers/wallets don't accept these credentials. the fact that someone issued a credential extending a known type does not imply that they are allowed to do so (or that they are a valid issuer at all)

This should be captured in a security consideration, ideally also in processing rules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant