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

Forbid KeyUpdate #11

Open
martinthomson opened this issue Nov 3, 2016 · 0 comments
Open

Forbid KeyUpdate #11

martinthomson opened this issue Nov 3, 2016 · 0 comments

Comments

@martinthomson
Copy link
Owner

With #8, we won't be using the TLS traffic secrets for key derivation. Because the application keys will be derived from the exporters, and exporters don't change over the lifetime of a connection, we will need to build an independent key schedule. As such, the TLS connection will be dead. The only reason that stream 1 might be needed after the conclusion of the handshake is to send more or updated NewSessionTicket messages.

KeyUpdate on the other hand will do nothing useful. We can ensure key freshness by updating the QUIC packet protection keys. Updating the redundant TLS application keys is pointless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant