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 18:00:59 +0000 (19:00 +0100)
commit9204e7ef0d186ed5005794ae0d6b14ad42ba274d
tree17b54983821235a00219b9145b9fbf5c325df26f
parent257df40f00cb487eee05d17b62d7d5b36908ecd2
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.

Conflicts:

ssl/d1_pkt.c
(cherry picked from commit 6f87807e629ee10ec0006b39d8851af8c5ade67b)
ssl/d1_pkt.c
ssl/d1_srvr.c