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 Privacy Considerations section on "phone home". #349

Merged
merged 6 commits into from
Jan 9, 2024

Conversation

msporny
Copy link
Contributor

@msporny msporny commented Nov 28, 2023

This pull request is an attempt to address issue #186 by adding a Privacy Considerations section on avoiding "phoning home".


Preview | Diff

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated
<a>issuer</a> about a specific <a>verifiable credential</a>. This
practice is known as "phoning home" and can result in a mismatch
in privacy expectations between <a>holders</a>, <a>issuers</a>,
<a>verifiers</a>, etc., as it allows <a>issuers</a> to correlate
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<a>verifiers</a>, etc., as it allows <a>issuers</a> to correlate
and <a>verifiers</a> as it allows <a>issuers</a> to correlate

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went with etc. because I didn't want to explicitly list subjects, who are invisible/silent participants, and there may be other such, beyond the trinity of Issuer, Holder, Verifier.

Replacing etc. with and removes subjects and any other non-trinity participants in the ecosystem from privacy consideration.

index.html Outdated
practice is known as "phoning home" and can result in a mismatch
in privacy expectations between <a>holders</a>, <a>issuers</a>,
<a>verifiers</a>, etc., as it allows <a>issuers</a> to correlate
<a>holders</a> with <a>verifiable credentials</a> without their
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<a>holders</a> with <a>verifiable credentials</a> without their
<a>holders</a> with <a>verifiable presentations</a> to <verifiers</a> without their

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think correlate <a>holders</a> with <a>verifiable presentations</a> to <verifiers</a> is accurate, because the issuer can't correlate verifiable presentations at all, because — even though the verifier only receives verifiable presentations of verifiable credentials — the issuer should never receive any verifiable presentation identifiers, only verifiable credential identifiers.

index.html Outdated Show resolved Hide resolved
index.html Outdated
<p>
Sometimes an <a>issuer</a> can be contacted to get status information in
a privacy-respecting manner, such as through a status list that provides
herd privacy. This is ok as long as the <a>issuer</a> is not able to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is that the term "herd" is to be avoided now to be replaced by "crowd" or "group". I'm not sure which we'd prefer.

Suggested change
herd privacy. This is ok as long as the <a>issuer</a> is not able to
group privacy. This is ok as long as the <a>issuer</a> is not able to

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
Copy link
Contributor

@David-Chadwick David-Chadwick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Subject to minor grammatical change

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
Copy link
Collaborator

@TallTed TallTed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@msporny msporny merged commit ca75b6b into main Jan 9, 2024
1 check passed
@msporny msporny deleted the msporny-avoid-phone-home branch January 9, 2024 20:33
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

Successfully merging this pull request may close these issues.

5 participants