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 sections on security/privacy and c14n method selection. #199

Merged
merged 4 commits into from
Sep 25, 2023

Conversation

msporny
Copy link
Member

@msporny msporny commented Sep 15, 2023

This PR attempts to address issue #194 and #195 by adding guidance on selecting canonicalization mechanisms, from a security and privacy perspective, as requested by the horizontal reviews performed on the vc-data-integrity specification.

/cc @kdenhartog


Preview | Diff

</p>
<p>
If an application utilizes JSON-LD or might require the selective disclosure
of information in a secured document, then using a cryptography suite that
Copy link
Member

Choose a reason for hiding this comment

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

This is probably my missing domain knowledge, but I do not understand the second half of the sentence ("or might require..."). Can you explain?

Copy link
Member

Choose a reason for hiding this comment

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

Yeah something grammatically doesn't seem correct here and I'm not picking up on what this is trying to say. Would be good to rephrase it I'm thinking.

Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, it made sense to me. It reads as: "If an application ... might require selective disclosure of information in a secured document" .

Copy link
Member

Choose a reason for hiding this comment

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

Ahh on re-reading this I figured out what was confusing for me. It would make sense if it's an AND because data-integrity is going to utilize JSON-LD and with SD then RDF-canon makes sense. If people just want SD without semantic security it's probably simpler to just point them to JWT-SD. Would we really want to point people at data integrity suites if they don't care about JSON-LD and want selective disclosure? Seems like forcing them to take on RDF-Canon if they only want SD without caring about the semantics is a bit more complex than necessary.

Copy link
Member Author

Choose a reason for hiding this comment

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

@kdenhartog I've added some language to point people to securing mechanisms that don't do canonicalization in this commit: 464ac07

Copy link
Member Author

Choose a reason for hiding this comment

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

@iherman and @kdenhartog I addressed the "and/or" issue via this commit: c3ffc66

Copy link
Member

@kdenhartog kdenhartog left a comment

Choose a reason for hiding this comment

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

One comment to address but other than that LGTM

</p>
<p>
If an application utilizes JSON-LD or might require the selective disclosure
of information in a secured document, then using a cryptography suite that
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, it made sense to me. It reads as: "If an application ... might require selective disclosure of information in a secured document" .

Copy link
Collaborator

@Wind4Greg Wind4Greg left a comment

Choose a reason for hiding this comment

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

I'll leave optimal wording to others. For me including that RDF canonicalization supports integrity of selective disclosure was key. Looks good.

@msporny
Copy link
Member Author

msporny commented Sep 25, 2023

Editorial, multiple reviews, changes requested and made, no objections, merging.

@msporny msporny merged commit 968b506 into main Sep 25, 2023
@msporny msporny deleted the msporny-c14n-sec-priv-considerations branch September 25, 2023 15:58
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.

6 participants