tree 0a1700432fa30706c7a19b33d89c6a9897a9bdf3
parent cf3d32697462903daaaa0e11bc9031e0366ffa46
author Jouni Malinen <jouni@qca.qualcomm.com> 1443714664 +0300
committer Glen Kuhne <kuh@google.com> 1506714651 -0700

Fix TK configuration to the driver in EAPOL-Key 3/4 retry case

Commit 7d711541dced759b34313477d5d163e65c5b0131 ('Clear TK part of PTK
after driver key configuration') started clearing TK from memory
immediately after having configured it to the driver when processing
EAPOL-Key message 3/4. While this covered the most common case, it did
not take into account the possibility of the authenticator having to
retry EAPOL-Key message 3/4 in case the first EAPOL-Key message 4/4
response is lost. That case ended up trying to reinstall the same TK to
the driver, but the key was not available anymore.

Fix the EAPOL-Key message 3/4 retry case by configuring TK to the driver
only once. There was no need to try to set the same key after each
EAPOL-Key message 3/4 since TK could not change. If actual PTK rekeying
is used, the new TK will be configured once when processing the new
EAPOL-Key message 3/4 for the first time.

Change-Id: I25ee11313f9059895ae5cf8f26f7f92fba39fbf0
Merged-In: I4ae5e929b3f442d6eaf77bf6b1d594c1feafdfdb
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Glen Kuhne <kuh@google.com>
Bug: 65245581