Bug#1003907: fails to successfully associate

[Michael Biebl]

Since I could easily reproduce it, I ran git bisect.

7a9c36722511ce4df88b76cceceb241d6c6a151e is the first bad commit
commit 7a9c36722511ce4df88b76cceceb241d6c6a151e
Author: Brian Norris <briannorris at chromium.org>
Date:   Fri Feb 28 15:50:47 2020 -0800

     DBus: Add "sae" to interface key_mgmt capabilities

     This will be present when the driver supports SAE and it's included in
     the wpa_supplicant build.

     Signed-off-by: Brian Norris <briannorris at chromium.org>


Reverting that commit on top of 2.10 I was again able to successfully 
establish a connection.

The debian build uses CONFIG_SAE=y.
Is it possible that wpasupplicant reports that the driver (iwlwifi) 
supports SAE but my hardware does not actually support SAE?

https://www.intel.com/content/www/us/en/support/articles/000054783/wireless.html

My network controller is an "Intel Corporation Centrino Advanced-N 6205"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/hostap/attachments/20220130/05b50fc7/attachment.sig>