From f03c8bc516a67f1e9f6f9631bc117e1f862072d3 Mon Sep 17 00:00:00 2001 From: Brian Warner Date: Sat, 25 Nov 2017 12:44:20 -0600 Subject: [PATCH] docs/client-protocol: update comment on ordering thanks jml for the catch --- docs/client-protocol.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/client-protocol.md b/docs/client-protocol.md index 331ccf6..64b1723 100644 --- a/docs/client-protocol.md +++ b/docs/client-protocol.md @@ -8,9 +8,12 @@ messages. Each such message contains a "phase" string, and a hex-encoded binary "body". -Any phase which is purely numeric (`^\d+$`) is reserved for application data, -and will be delivered in numeric order. All other phases are reserved for the -Wormhole client itself. Clients will ignore any phase they do not recognize. +Any phase which is purely numeric (`^\d+$`) is reserved for encrypted +application data. The Rendezvous server may deliver these messages multiple +times, or out-of-order, but the wormhole client will deliver the +corresponding decrypted data to the application in strict numeric order. All +other (non-numeric) phases are reserved for the Wormhole client itself. +Clients will ignore any phase they do not recognize. Immediately upon opening the mailbox, clients send the `pake` phase, which contains the binary SPAKE2 message (the one computed as `X+M*pw` or