forked from google/boringssl
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Keep the encryption state and encryption level in sync.
This is a little bit of internal cleanup. The original intent was so QUIC could install secrets in set_(read|write)_state, but that was somewhat annoying, so I've left it just before the call for now. There is one TLS 1.3 state transition which doesn't carry an encryption level: switching from 0-RTT keys back to unencrypted on an HRR-based 0-RTT reject. The TCP code doesn't care about write_level and the QUIC code is currently fine because we never "install" the 0-RTT keys. But we should get this correct. This also opens the door for DTLS 1.3, if we ever implement it, because DTLS 1.3 will need to know which level it is to handle 0-RTT keys funny. (Clients sending 0-RTT will briefly have handshake and 0-RTT write keys active simultaneously.) QUIC has the same property, but we can fudge it because only the caller is aware of this. Change-Id: Ia76d787e1b96a058d9818948b6d9a051e8592207 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40124 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com>
Showing
6 changed files
with
34 additions
and
28 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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