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

Allow a future extension to allow external PSKs and certificate-based… #1117

Merged
merged 3 commits into from
Dec 27, 2017
Merged

Allow a future extension to allow external PSKs and certificate-based… #1117

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9ca2f9f
Allow a future extension to allow external PSKs and certificate-based…
russhousley Dec 7, 2017
4fad920
Accept rewording suggested by kaduk
russhousley Dec 9, 2017
a05266a
Adopt wording suggested by Gerasymchuk
russhousley Dec 10, 2017
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
4 changes: 2 additions & 2 deletions draft-ietf-tls-tls13.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5747,9 +5747,9 @@ the PSK binder. {{PSK-FINISHED}}
describes a concrete attack on constructions that do not bind to
the server's certificate (see also {{Kraw16}}). It is unsafe to use certificate-based client
authentication when the client might potentially share the same
PSK/key-id pair with two different endpoints. Implementations MUST NOT combine
PSK/key-id pair with two different endpoints. Implementations MUST NOT combine
external PSKs with certificate-based authentication of either the
client or the server.
client or the server unless negotiated by some extension.

If an exporter is used, then it produces values which are unique
and secret (because they are generated from a unique session key).
Expand Down