Only enable DTLS post-handshake rexmits if we sent the final Finished.
I messed up https://boringssl-review.googlesource.com/8883 and caused
both sides to believe they had sent the final Finished. Use next_message
to detect whether our last flight had a reply.
Change-Id: Ia4d8c8eefa818c9a69acc94d63c9c863293c3cf5
Reviewed-on: https://boringssl-review.googlesource.com/19604
Reviewed-by: Steven Valdez <svaldez@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
diff --git a/ssl/test/runner/common.go b/ssl/test/runner/common.go
index b402f38..bf56ca2 100644
--- a/ssl/test/runner/common.go
+++ b/ssl/test/runner/common.go
@@ -886,6 +886,10 @@
// and include a copy of the full one.
MixCompleteMessageWithFragments bool
+ // RetransmitFinished, if true, causes the DTLS Finished message to be
+ // sent twice.
+ RetransmitFinished bool
+
// SendInvalidRecordType, if true, causes a record with an invalid
// content type to be sent immediately following the handshake.
SendInvalidRecordType bool