Skip to content

Commit 4a1ca37

Browse files
paolo-de-rosadavid-bakkerphin10MichaelStausholm
authored
Release/topics a c d latest (#406)
* Update a-privacy-risks-and-mitigations.md Solving FR follow-up on comment resolution. * Update c-wallet-unit-attestation.md Mostly editorial changes * Update c-wallet-unit-attestation.md Re-inserting missing text. * Update c-wallet-unit-attestation.md Addition to WUA_08 * Update c-wallet-unit-attestation.md some last changes. * Addressed some PR comments. * Removed WUA_9a proposal. * Minor editorials. * Update d-embedded-disclosure-policies.md Updated --------- Co-authored-by: David Bakker <75264147+david-bakker@users.noreply.github.com> Co-authored-by: Paul Hin <phin@scytales.com> Co-authored-by: Michael Stausholm <michael.stausholm@alexandra.dk>
1 parent e75d7d5 commit 4a1ca37

File tree

3 files changed

+263
-230
lines changed

3 files changed

+263
-230
lines changed

docs/discussion-topics/a-privacy-risks-and-mitigations.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -371,17 +371,15 @@ corresponding User, and to track at which Relying Parties the User
371371
presents their attestations.
372372

373373
Unlike for Relying Party linkability, Attestation Provider linkability
374-
cannot be prevented for attestations using salted-attribute hashes. The
374+
cannot be technically prevented for attestations using salted-attribute hashes. The
375375
only way to technically mitigate this risk is by using Zero-Knowledge
376-
Proofs instead, as described in section 5. However, as for Relying Party
377-
linkability, organisational and repressive measures can be used to
376+
Proofs instead, as described in section 5. However, like for Relying Party
377+
linkability, organisational preventive, detective, and repressive measures can be used to
378378
discourage Attestation Providers from colluding and tracking Users
379-
and to mitigate Attestation Provider linkability. In
379+
and to mitigate Attestation Provider linkability. For example, Attestation Providers may purposely discard
380+
the unique values of an attestation after it has been issued, or remove any links to the User to whom it has been issued. In
380381
addition, many Attestation Providers are subject to regular audits,
381-
which means that collusion and tracking can more easily be detected.
382-
For example, detecting if Attestation Providers may purposely discard
383-
certain unique values of an attestation or forget the user for whom
384-
it has been issued.
382+
which means that collusion and tracking can more easily be detected by relevant authorities. Finally, Attestation Providers that are found to be tracking their Users in an illegal manner can be fined, have their access certificates revoked, or be otherwise punished.
385383

386384
### 2.4 WUAs and Wallet Providers
387385

0 commit comments

Comments
 (0)