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

Require only support for PSK-(EC)DHE #3839

Closed
ekr opened this issue Jul 8, 2020 · 1 comment · Fixed by #3866
Closed

Require only support for PSK-(EC)DHE #3839

ekr opened this issue Jul 8, 2020 · 1 comment · Fixed by #3866
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing

Comments

@ekr
Copy link
Collaborator

ekr commented Jul 8, 2020

S 7. Claims

  * 1-RTT keys have forward secrecy

This is only true if you only resume with PSK-(EC)DHE, but I don't see a requirement for this. So we need to either require this or change the text.
@martinthomson
Copy link
Member

This obsession with forward secrecy is a hang-up from Google QUIC. I think that we should instead say that 1-RTT keys are derived from the completed cryptographic handshake instead.

martinthomson added a commit that referenced this issue Jul 8, 2020
@martinthomson
Remove claim about 1-RTT keys
d79bdc5 
This claim isn't necessary, as the statement about suitability is what
matters here.

Closes #3839.
@martinthomson martinthomson added -transport editorial An issue that does not affect the design of the protocol; does not require consensus. labels Jul 8, 2020
@martinthomson martinthomson mentioned this issue Jul 8, 2020
Merged
@larseggert larseggert added this to Triage in Late Stage Processing via automation Jul 8, 2020
@mnot mnot moved this from Triage to Editorial Issues in Late Stage Processing Jul 9, 2020
Late Stage Processing automation moved this from Editorial Issues to Issue Handled Jul 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
Late Stage Processing
  
Issue Handled
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove claim about 1-RTT keys quicwg/base-drafts
2 participants
@martinthomson @ekr