Skip to content

Security considerations for reusing keys in multiple key establishments #1408

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

Open
emanjon wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Security considerations for reusing keys in multiple key establishments #1408

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
2 changes: 2 additions & 0 deletions draft-ietf-tls-rfc8446bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5394,6 +5394,8 @@ cache lookups in web browsers.
Clients and Servers SHOULD NOT reuse a key share for multiple connections. Reuse
of a key share allows passive observers to correlate different connections. Reuse
of a client key share to the same server additionally allows the server to correlate different connections.
Additionally, if a key is reused in multiple key-establishment operations, i.e., a static key, this
Copy link
Contributor

@muhammad-usama-sardar muhammad-usama-sardar Mar 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I propose to add a reference to static key.

undermines forward secrecy and makes exploitation of side-channel attacks and implementation flaws much easier.

It is RECOMMENDED that the labels for external identities be selected so that they
do not provide additional information about the identity of the
Expand Down