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:53:19 +0000 (18:53 +0100)
commitb62f4daac00303280361924b9cc19b3e27528b15
tree5cb0356e44d092695a8d2bf5481bf44bcbe89d35
parent0c75eeacd3285b395dc75b65c3e6fe6ffbef59f0
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.
ssl/d1_pkt.c
ssl/d1_srvr.c