Open
Conversation
annevk
reviewed
Jun 14, 2019
| the new API does not make it any easier to identify or track users. | ||
|
|
||
| <h3>Padding Opaque Responses</h3> | ||
| TODO: Recommend padding for opaque responses. |
Member
There was a problem hiding this comment.
This is quite important to add if we're going to say anything at all, in particular as it contradicts some of the information stated above.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change adds a new section that discusses the security and privacy considerations, specifically around potential side-channel attacks.
Preview | Diff