I wanted to bring to the list a suggestion Jonathan Hoyland might at the mic line today.
During the Supplemental Authentication discussion, several people brought up the idea of using exporters and channel bindings (9261, 9266). Yaroslav pointed out that it requires application changes to use them. Jonathan suggested a “pause” extension. Rather than changing the handshake, this new extension would tell the peer that more data is coming and do not accept/send application data until the pause is lifted. He and I chatted after the session, and we realized this could probably handle multi-exchange PAKE traffic as well. Anything that would modify the handshake, or is normally post-handshake (cough, authentication, cough) would also work. Probably need to nail down the semantics such as when to lift the pause (E.g., when you don’t get records with the pause extension or wait until the “done” message is sent, etc), but this seems to me like an elegant solution. during the presentation on Suppl During the Supplemental
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
