You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The referenced document is BSI TR-2012-1, which chains to the CatKDF defined in ETSI TS 103 744, which is:
Input:
psk - a secret key. It may be present. If not present this value shall be the empty octet string, ∅.
(k 1, k 2, …, k n) - n-tuple of octet strings containing shared secrets k i, exchanged through a hybrid key exchange, see
Figure 4.
MA, MB - octet string of a pair of exchanged messages in establishment of the shared secrets k i.
context - octet string context set by the instance of the key exchange transaction - this may include a transcript of
additional exchanged messages.
label - an octet string that specifies a separation of use for the application or instance of the key-exchange. Any labels
used in the key exchange should not be provided as an argument to the same hash function for another purpose in the
application.
length - the length in octets of the derived key material key_material.
Process:
1) Form secret = psk || k1 || k 2 || … || k n.
2) Set f_context = f(context, MA, MB), where f is a context formatting function.
3) key_material = KDF(secret, label, f_context, length).
4) Return key_material.
Output:
key_material - derived key material.
CatKDF does not include the public keys, but it does include both ciphertexts.
Peter C also makes a good point about the intro text. I'll adjust that. And I'll add a note about BSI / ETSI CatKEM.
See comment from Peter C:
https://mailarchive.ietf.org/arch/msg/spasm/Fq06ghviNMejesJNR4XzP5x0ecI/
The text was updated successfully, but these errors were encountered: