DTLS message_sequence number wrong in rehandshake ServerHello
authorMichael Tuexen <tuexen@fh-muenster.de>
Tue, 13 Aug 2013 17:53:19 +0000 (18:53 +0100)
committerDr. Stephen Henson <steve@openssl.org>
Tue, 13 Aug 2013 17:59:41 +0000 (18:59 +0100)
commit6f87807e629ee10ec0006b39d8851af8c5ade67b
tree5b159bc1d7dc68387b8a8a05da942d1bbfc185ad
parent799f203ff6933807f43e9e0692ec2741d4d83d59
DTLS message_sequence number wrong in rehandshake ServerHello

This fix ensures that
* A HelloRequest is retransmitted if not responded by a ClientHello
* The HelloRequest "consumes" the sequence number 0. The subsequent
ServerHello uses the sequence number 1.
* The client also expects the sequence number of the ServerHello to
be 1 if a HelloRequest was received earlier.
This patch fixes the RFC violation.
(cherry picked from commit b62f4daac00303280361924b9cc19b3e27528b15)

Conflicts:

ssl/d1_pkt.c
ssl/d1_pkt.c
ssl/d1_srvr.c