Conversation
Compared to firefox 120, changes seem to include: - added `X25519MLKEM768` in keyshare and supported curves - added signed certificate timestamp extension - added compress certificate extension
Member
Author
|
Firefox is reusing the x25519 part for its X25519 and X25519MLKEM768 keyshares, different from the chrome behavior in #342 |
Contributor
|
@mingyech 其实我觉得 Chrome 的做法有点浪费，但我猜是实现方式不同的原因，Chromium 里现在可能是每个密钥交换方式都对应着单独的函数，为未来某一天去掉 X25519 做准备 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Compared to firefox 120, changes seem to include:
X25519MLKEM768in keyshare and supported curves