fixup! fixup! fixup! fixup! Adds DTLS 1.3 ACK message functionality

fwh-dc · Aug 7, 2024 · f53e668 · f53e668
1 parent bd492eb
commit f53e668
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/doc/designs/dtlsv1_3/dtlsv1_3-main.md b/doc/designs/dtlsv1_3/dtlsv1_3-main.md
@@ -72,8 +72,8 @@ ACK's are sent for KeyUpdates, NewSessionTicket and Finish (client).
 Notes on RFC9147 Section 7.1:
 
 * The implementation does not offer any logic to determine that there is disruption
-when receiving messages which means it will not send ACKs for the example given
-in RFC9147 Figure 12.
+  when receiving messages which means it will not send ACKs for the example given
+  in RFC9147 Figure 12.
 * ACKs are always sent immediately after receiving a message to be ACK'ed.
 * Empty ACKs are never sent.
 

diff --git a/test/recipes/70-test_dtls13ack.t b/test/recipes/70-test_dtls13ack.t
@@ -18,7 +18,7 @@ my $test_name = "test_dtls13ack";
 setup($test_name);
 
 plan skip_all => "TLSProxy isn't usable on $^O"
-    if $^O =~ /^(VMS)$/;
+    if $^O =~ /^(VMS)$/ || $^O =~ /^(MSWin32)$/;
 
 plan skip_all => "$test_name needs the dynamic engine feature enabled"
     if disabled("engine") || disabled("dynamic-engine");