@@ -716,7 +716,7 @@ The following steps describe the Diffie-Hellman key exchange protocol
716
716
(DHKEXid15), as part of the verification of the Ownership Voucher:
717
717
718
718
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
720
720
721
721
1 . The values “p” and “g” are chosen from
722
722
[[ 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
932
932
randoms when used with larger SEK and SVK for future crypto. Please contact
933
933
the Secure Device Onboard Enablement team for details.**
934
934
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.
937
937
938
938
#### Key Derivation Function
939
939
@@ -968,8 +968,8 @@ bits (see Table 3):
968
968
969
969
!!! Note
970
970
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.
973
973
974
974
The above strings are ASCII with no terminator character (that is, C ‘&bsol ; 000’
975
975
terminator is not included).
0 commit comments