[PATCH] wpa_supplicant: Cache PMK for 802.1X 4-way handshake offload

[Jouni Malinen]

On Mon, Aug 03, 2026 at 06:41:46PM +0800, Chung-Hsien Hsu wrote:
> This fixes a functional issue.
> 
> With IEEE 802.1X 4-way handshake offload, the normal host-side EAPOL-Key
> processing path is bypassed, so the PMK is not stored in the WPA state
> machine and no PMKSA cache entry is created.
> 
> As a result, a subsequent connection cannot use PMKSA caching and may
> require a full EAP authentication again.

It would be good to state that more clearly in the commit message since
that part about PMKSA caching not being available was not obvious since
the focused more on storing the PMK rather than adding a PMKSA cache
entry.

> This change stores the PMK and
> creates the PMKSA cache entry for the applicable non-FT and non-Suite-B
> RSN cases.

If the main point here is in adding that PMKSA cache entry, why the
changes allow wpa_sm_set_pmk() to be called with auth_addr == NULL which
is explicitly documented to not cache the PMK? I can understand the need
to create a PMKSA cache entry, but what is the need, if any, to set
sm->pmk?

-- 
Jouni Malinen                                            PGP id EFC895FA