diff options
author | Jan Dittberner <jandd@cacert.org> | 2018-10-31 03:21:34 +0100 |
---|---|---|
committer | Jan Dittberner <jandd@cacert.org> | 2018-10-31 03:21:34 +0100 |
commit | ac241bf496ff082c7c83112f75d5404626cda64e (patch) | |
tree | 8c3bd7040aaa37790f6dbdd9b011498a2c36c4fa | |
parent | 9b2f064b207cbd46acf645da817766c2e2ec53f8 (diff) | |
download | cacert-codedocs-ac241bf496ff082c7c83112f75d5404626cda64e.tar.gz cacert-codedocs-ac241bf496ff082c7c83112f75d5404626cda64e.tar.xz cacert-codedocs-ac241bf496ff082c7c83112f75d5404626cda64e.zip |
Fix inaccuracy in signer protocol specification
-rw-r--r-- | source/signer.rst | 11 |
1 files changed, 4 insertions, 7 deletions
diff --git a/source/signer.rst b/source/signer.rst index 2e7b28b..643adf5 100644 --- a/source/signer.rst +++ b/source/signer.rst @@ -19,9 +19,10 @@ Protocol request data is encoded in the following format: Byte Data ======= ============================================================== 0-2 length of header + data in network byte order - 3-12 action specific header - 13-15 length of first action specific content in network byte order - 15-N fist action specific content string + 3-5 length of header network byte order [#diff-to-request]_ + 6-14 action specific header + 15-17 length of first action specific content in network byte order + 18-N fist action specific content string N+1-N+3 length of second action specific content in network byte order N+4-M second action specific content string M+1-M+3 lenght of third action specific content in network byte order @@ -280,10 +281,6 @@ Protocol response data is encoded in the following format: M+4-End payload data 3 ======= ======================================================= -.. [#diff-to-request] this is a difference to the - :ref:`signer-request-data-format` that does not add the - length of the header - General response header format ------------------------------ |