Repeat - critical to define a Qualified Pseudonym PAD document #322
PriwayChromeRoads
started this conversation in
Security & Privacy
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The by far biggest problem in the ARF specifications is the assumption of linkable identification as unlinkable identification must be both the default and preferred outcome.
This problem start with the assumption that PAD certificates are with name instead of merely a unlinkable pseudonym outside the issuing context. The main destructive consequence being that all issuance must involve linkable identification.
A simple use case could be a relaying party provided with credentials for an unlinkable identity which create new data that can be reused elsewhere - such a relaying party can both be a CA issuer and a credential issuer linking only to the pseudonym context. In practice, all CA entities are also relaying parties and all relaying parties can also be CAs.
Beta Was this translation helpful? Give feedback.
All reactions