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

secdir review of -qpack; issue 2 #4400

Closed
larseggert opened this issue Nov 20, 2020 · 2 comments
Closed

secdir review of -qpack; issue 2 #4400

larseggert opened this issue Nov 20, 2020 · 2 comments
Labels
-qpack ietf-lc An issue that was raised during IETF Last Call.
Milestone

Comments

@larseggert
Copy link
Member

Magnus Nystrom wrote:

While there are several options listed, there is also no recommendation
as to what strategy (option) implementations should choose to protect
against this attack. It seems like the Never-Indexed-Literal is a good
candidate which should be easy to implement.

@larseggert larseggert added -qpack ietf-lc An issue that was raised during IETF Last Call. labels Nov 20, 2020
@larseggert larseggert added this to the qpack-secdir milestone Nov 20, 2020
@larseggert larseggert added this to Triage in Late Stage Processing via automation Nov 20, 2020
@martinthomson
Copy link
Member

Context?

@MikeBishop
Copy link
Contributor

This is the second paragraph of the question which is #4399; closing as a duplicate and moving this paragraph over there.

Late Stage Processing automation moved this from Triage to Issue Handled Nov 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-qpack ietf-lc An issue that was raised during IETF Last Call.
Projects
Late Stage Processing
  
Issue Handled
Development

No branches or pull requests

3 participants