eapoltest: In hostapd 2.10 and earlier, the PKEX code remains active even after asuccessful PKEX association

In hostapd 2.10 and earlier, the PKEX code remains active even after asuccessful PKEX association. An attacker that successfully bootstrappedpublic keys with another entity using PKEX in the past, will be able tosubvert a future bootstrapping by passively observing public keys, re-usingthe encrypting element Qi and subtracting it from the captured message M (X= M - Qi). This will result in the public ephemeral key X; the only elementrequired to subvert the PKEX association.

Where it's fixed