[Pkg-privacy-commits] [libotr] 11/20: Clarify fragmentation format in Protocol-v3.html

[Intrigeri]

This is an automated email from the git hooks/post-receive script.

intrigeri pushed a commit to annotated tag 4.1.1
in repository libotr.

commit aece877f3904f0b39816da8eda3da337f392fc98
Author: Ian Goldberg <iang at cs.uwaterloo.ca>
Date:   Thu Mar 3 18:56:00 2016 +0100

    Clarify fragmentation format in Protocol-v3.html
    
    Clarify that instance tags and fragment numbers in the OTR fragment
    format are allowed to have leading 0s.
    
    Thanks to Ola Bini <obini at thoughtworks.com> for the report.
    
    Fixes #107
    
    Signed-off-by: Ian Goldberg <iang at cs.uwaterloo.ca>
    Signed-off-by: David Goulet <dgoulet at ev0ke.net>
---
 Protocol-v3.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Protocol-v3.html b/Protocol-v3.html
index 99c376b..b76bca5 100644
--- a/Protocol-v3.html
+++ b/Protocol-v3.html
@@ -1280,7 +1280,8 @@ fragmentation on outgoing messages is optional.</p>
 
     <li>Note that k and n are unsigned short ints (2 bytes), and each has
       a maximum value of 65535.  Also, each piece[k] must be
-      non-empty.</li>
+      non-empty.  The instance tags (if applicable) and the k and n
+      values may have leading zeroes.</li>
     </ul>
     <p>Note that fragments are not themselves messages that can be
     fragmented: you can't fragment a fragment.</p></dd>

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-privacy/packages/libotr.git