projects / openssl.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f922dac) | patch
Process KeyUpdate and NewSessionTicket messages after a close_notify
authorMatt Caswell <matt@openssl.org>
Tue, 4 Sep 2018 12:36:55 +0000 (13:36 +0100)
committerMatt Caswell <matt@openssl.org>
Fri, 7 Sep 2018 10:15:20 +0000 (11:15 +0100)
commit1bf4cb0fe3b00e1c501a04ace4e3e3145314cb20
tree8b44f632a8520381c4843c7399a46032ebdbbbc2tree | snapshot
parentf922dac87d859cc7419207301533fe89582ac3eacommit | diff
Process KeyUpdate and NewSessionTicket messages after a close_notify

If we've sent a close_notify then we are restricted about what we can do
in response to handshake messages that we receive. However we can sensibly
process NewSessionTicket messages. We can also process a KeyUpdate message
as long as we also ignore any request for us to update our sending keys.

Reviewed-by: Tim Hudson <tjh@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/7114)
ssl/record/rec_layer_s3.c diff | blob | history
ssl/statem/statem_clnt.c diff | blob | history
ssl/statem/statem_lib.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.