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
In Sender Key Derivation, the KeyRatchet is created based on a 16byte value, but when advancing the generation, a 32byte output is required to calculate the next internal state of the KeyRatchet. This violates the PRK requirements of RFC5869 HMAC-based Extract-and-Expand Key Derivation Function (HKDF) Section 2.3.
PRK a pseudorandom key of at least HashLen octets
It's probably not a problem security-wise in this case, but some libraries check for this requirement and it's a pure inconvenience.
The text was updated successfully, but these errors were encountered:
tignear
changed the title
Indirectly violates RFC5869 Section 2.2
Indirectly violates RFC5869 Section 2.3
Oct 5, 2024
This specification creates a situation that indirectly violates RFC5869 HMAC-based Extract-and-Expand Key Derivation Function (HKDF) Section 2.3.
In Sender Key Derivation, the KeyRatchet is created based on a 16byte value, but when advancing the generation, a 32byte output is required to calculate the next internal state of the KeyRatchet. This violates the PRK requirements of RFC5869 HMAC-based Extract-and-Expand Key Derivation Function (HKDF) Section 2.3.
It's probably not a problem security-wise in this case, but some libraries check for this requirement and it's a pure inconvenience.
The text was updated successfully, but these errors were encountered: