Reorganize Security and privacy considerations #216
Merged
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.
@pes10k PTAL. After another look of your insightful privacy review feedback (thanks again!) I think this PR should fix:
Specify what kind of attacks are considered and addressed #204
Added a top-level "Types of privacy and security threats" section seeded with timing attacks description as a type of side-channel attack worth mitigating against in this (as well as any other) web spec.
"no side channels" subsection issues #205
This confusing section was removed to prepare for integration of your proposed cross-site covert channel attack description.
Remaining work:
This lays the foundation for @pes10k to contribute the proposed cross-site covert channel attack discussed in #197 (or the WG can integrate on your behalf with credits, possibly in another PR).
Preview | Diff