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

PSK context for 0-RTT needs version number #1003

Merged
merged 1 commit into from
May 4, 2017
Merged

PSK context for 0-RTT needs version number #1003

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
PSK context for 0-RTT needs version number 
The 0-RTT key might differ between TLS versions (as demonstrated with
the draft -20 changes). Be explicit about storing this version number
since section 4.2.9 requires this information too.
  • Loading branch information
@Lekensteyn
Lekensteyn committed May 2, 2017
commit 1a71021393c0f15d6a90a03a01918e4adb698f53
1 change: 1 addition & 0 deletions draft-ietf-tls-tls13.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1313,6 +1313,7 @@ the server and to encrypt the early data.
When clients use a PSK obtained externally to send early data, then the following
additional information MUST be provisioned to both parties:

* The TLS version number for use with this PSK
* The cipher suite for use with this PSK
* The Application-Layer Protocol Negotiation (ALPN) protocol, if any is to be used
* The Server Name Indication (SNI), if any is to be used
Expand Down