Issues
--
* tlswg/tls13-spec (+2/-0/💬35)
2 issues created:
- Should x25519 be made MTI? (by sftcd)
https://github.com/tlswg/tls13-spec/issues/1359
- Require sending MTI curves in CH.key_share (by ekr)
https://github.com/tlswg/tls13-spec/issues/1358
2 issues received 35 new com
On 08/06/2024 11:07, Peter Gutmann wrote:
when the dominant platform only offers 25519 then the the only option
you have (unless you want to do the HRR dance) is to select that,
whether you want it or not.
The recently adopted Key Share Prediction draft [1] allows servers to
signal which key
Dennis Jackson writes:
>The recently adopted Key Share Prediction draft [1] allows servers to signal
>which key shares they'd like to see.
Sure, but that both assumes you've got DNS in operation and that client and
server will go through the DNS backchannel to set up TLS parameters before
trying
