tree 643ed7211b0e65841782b547abc72f74256bba4b
parent 746ed338bc00bd01417f620b90799b8bfe7a509e
author Vinayak Yadawad <vinayak.yadawad@broadcom.com> 1655377786 +0530
committer Sunil Ravi <sunilravi@google.com> 1660931462 +0000

ASSOC: Mark Port authorization and State Completion based
on authorized state in connect event

In case of drivers supporting 4way handshake offload, mark port
authorized and state completion only if driver advertizes authorized
state in the connect event. Otherwise there are fair chances of driver
port authorization api gets called while 4-way handshake is in progress
at the lower layer.
In order to avoid this possible race condition always update port
authorization and supplicant state WPA_COMPLETED setting from
EVENT_PORT_AUTHORIZED context when driver is done with 4way handshake.

Additionally there is change to avoid plumbing PSK during initial
assoc as its done during initial connect in case of 4-way handshake
offload.
The CL includes change to address additional PMK length to support newer
key mgmt like SUITEB-192.

Bug: 236661101
Test: Validated the different security connections/roam on Hikey platform

Signed-off-by: Vinayak Yadawad <vinayak.yadawad@broadcom.com>
Change-Id: I2c438ca961fe7e6d70d6d013035362dd94488b15