Adds security and privacy section to the spec. #133
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
btolsch
reviewed
Jan 9, 2019
markafoltz
changed the title
pthatcherg
reviewed
Jan 12, 2019
pthatcherg
reviewed
Jan 14, 2019
Co-Authored-By: mfoltzgoogle <[email protected]>
Co-Authored-By: mfoltzgoogle <[email protected]>
Co-Authored-By: mfoltzgoogle <[email protected]>
Co-Authored-By: mfoltzgoogle <[email protected]>
Co-Authored-By: mfoltzgoogle <[email protected]>
Co-Authored-By: mfoltzgoogle <[email protected]>
Co-Authored-By: mfoltzgoogle <[email protected]>
|
@pthatcherg @btolsch I believe I've resolved all outstanding comments, and I'm going to merge now. All should free to file any additional topics as issues with tag Security. There are already several open items which will require further work on this section or the Authentication section of the spec. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses Issue #13: Propose security mechanisms for the OSP
This is a draft version of the Security and Privacy section of the Open Screen Protocol spec, following the W3C's Security and Privacy Questionnaire [1]. It addresses the following:
Would appreciate wide review. In particular, if there are topics from previous discussions missing, can add them here or in a followup PR.
[1] https://www.w3.org/TR/security-privacy-questionnaire/#questions