Skip to content
This repository was archived by the owner on Aug 20, 2024. It is now read-only.

Commit 50a7ca0

Browse files
committed
Fix Issue 29 and 36
Signed-off-by: Chandrakar, Prateek <prateek.chandrakar@intel.com>
1 parent 52d834c commit 50a7ca0

File tree

2 files changed

+5
-6
lines changed

2 files changed

+5
-6
lines changed

docs/protocol-specification/protocol-data-types.md

-1
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,6 @@ string is *((n+2)/3)\*4*, using integer arithmetic.[^5]
123123
2 4 ab YWI=
124124
3 4 abc YWJj
125125
4 8 abcd YWJjZA==
126-
5 8 abcde YWJjZGU=
127126

128127

129128
To simplify the parser, we specify that ByteArrays always contain encoded data

docs/protocol-specification/protocol-description.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -716,7 +716,7 @@ The following steps describe the Diffie-Hellman key exchange protocol
716716
(DHKEXid15), as part of the verification of the Ownership Voucher:
717717

718718
1. The Device and Owner each choose random numbers (Owner: a, Device: b), and
719-
encode these numbers into exchanged parameters A = ga mod p, and B = gb mod
719+
encode these numbers into exchanged parameters A = g<sup>a</sup> mod p, and B = g<sup>b</sup> mod p
720720

721721
1. The values “p” and “g” are chosen from
722722
[[RFC3526]] , with sizes as follows:
@@ -932,8 +932,8 @@ concatenation, and blen(x) length of x in bytes. The output of blen(x) is a
932932
randoms when used with larger SEK and SVK for future crypto. Please contact
933933
the Secure Device Onboard Enablement team for details.**
934934

935-
- Shy is not used to compute the shared secret ShSe because it can be derived
936-
from Shx and the curve equation. Hence it provides no additional entropy.
935+
- Sh<sub>y</sub> is not used to compute the shared secret ShSe because it can be derived
936+
from Sh<sub>x</sub> and the curve equation. Hence it provides no additional entropy.
937937

938938
#### Key Derivation Function
939939

@@ -968,8 +968,8 @@ bits (see Table ‎3):
968968

969969
!!! Note
970970
The operation is HMAC-SHA-256[key, value], so the zero argument above
971-
indicates a HMAC with key of zero (0). Since HMAC keys are zero padded (See
972-
), this should be sufficient to generate a consistent HMAC operation.
971+
indicates a HMAC with key of zero (0). Since HMAC keys are zero padded,
972+
this should be sufficient to generate a consistent HMAC operation.
973973

974974
The above strings are ASCII with no terminator character (that is, C ‘&bsol;000’
975975
terminator is not included).

0 commit comments

Comments
 (0)