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.

Sign up for GitHub

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

Jump to bottom

Security and privacy considerations #70

Closed
philarcher opened this issue Jan 20, 2023 · 1 comment · Fixed by #172
Closed

Security and privacy considerations #70

philarcher opened this issue Jan 20, 2023 · 1 comment · Fixed by #172
Labels
documentation Improvements or additions to documentation HorizontalReview ms:CR

Comments

@philarcher
Copy link
Contributor

philarcher commented Jan 20, 2023 •
edited
Loading

This just a place where we can discuss any security and privacy issues that we think might arise from the spec. Looking at the self-assessment form it doesn't look like we will have much to worry about but we need to consider this carefully.
@philarcher philarcher added the documentation Improvements or additions to documentation label Jan 20, 2023
@philarcher philarcher changed the title Security considerations Security and privacy considerations Jan 20, 2023
@yamdan yamdan mentioned this issue Mar 13, 2023
Closed
@gkellogg gkellogg added the ms:CR label May 10, 2023
dlongley added a commit that referenced this issue May 24, 2023
@dlongley
Add security considerations text.
c0721fe 
- Addresses #70.
@dlongley dlongley mentioned this issue May 24, 2023
Merged
dlongley added a commit that referenced this issue Jun 7, 2023
@dlongley @yamdan @TallTed
Add security considerations text. (#106)
e98a348 
* Add security considerations text.

- Addresses #70.

* Fix closing tags in Security Considerations section.

* Fix typo in Security Considerations section.

Co-authored-by: Dan Yamamoto <[email protected]>

* Simplify suggested mitigation language.

Co-authored-by: Ted Thibodeau Jr <[email protected]>

* Use "canonicalize" language over "canonize".

---------

Co-authored-by: Dan Yamamoto <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
This was referenced Jun 9, 2023
Closed
Open
Closed
@philarcher
Copy link
Contributor Author

This was discussed 2023-09-11 (see below https://www.w3.org/2023/09/11-rch-minutes.html#t05). Group feels the issue has been addressed fully. Text to include new reference to the Data Integrity spec for more info.

gkellogg added a commit that referenced this issue Sep 11, 2023
@gkellogg
Reference vc-data-inegrity.
c52b2b8 
Remove issue marker for #70.

Fixes #70.
@gkellogg gkellogg mentioned this issue Sep 11, 2023
Merged
gkellogg added a commit that referenced this issue Sep 11, 2023
@gkellogg
Reference vc-data-inegrity.
48cb68d 
Remove issue marker for #70.

Fixes #70.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation HorizontalReview ms:CR
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reference vc-data-inegrity. w3c/rdf-canon
2 participants
@gkellogg @philarcher