PMK cache sync with driver

Gautam Kotekoppa Ravikrishna Gautam.Ravikrishna
Mon Jul 5 10:08:31 PDT 2010



If my understanding is correct, for drivers that use their own RSN IEs
during association, a PMKID list is kept in the driver. This list is
kept in sync with its own list by the supplicant using add_pmkid,
remove_pmkid calls. Browsing through the supplicant code I cant find
where the driver's PMKID entry is removed when a PMK cache entry is
removed in the supplicant.

One of the problems due to this is when a cache entry expires on the
station, the supplicant removes its own entry. Unaware, driver sends the
corresponding PMKID during reassociation and the AP jumps to 4 way
handshake. Handshake fails as supplicant is unable to find the entry.
This loss of sync leads to endless failed association attempts and stops
only when the AP does a full authentication. Understandably, some APs
never do a full authentication if a valid PMKID is found during

Am I missing something or is this really a problem?



Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Hostap mailing list