Re: Bug#982548: wpasupplicant: Missing support for WPA-EAP-SUITE-B(-192)
Control: tag -1 wontfix
Control: fixed -1 2:2.6-4
On Thu, 11 Feb 2021, at 16:50, Jan Fuchs wrote:
> Package: wpasupplicant
> Version: 2:2.4-1
> Severity: normal
> Tags: patch
> It was observed that Debian's wpa_supplicant is not able to connect to
> connect to networks with key_mgmt WPA-EAP-SUITE-B and/or
> WPA-EAP-SUITE-B-192 (aka WPA3-Enterprise 192-bit mode). The upstream
> wpa_supplicant supports this since 2.4. Following is seen when trying
> to load a config with this kind of configuration:
I’m afraid 2:2.4-1 is part of Debian Stretch, which is no longer supported. You can, however, install a newer version from stretch-backports, but I’d rather recommend you to upgrade to Buster; please be aware that Bullseye is likely going to be released later this year.
Alternatively, the Debian LTS project might consider enabling this even though it’s not technically in their scope, as this is not a security issue (cc'ed the LTS mailing list), but I’m personally not interested in supporting such an old version.
> 1613046731.169674: Line: 3 - start of a new network block
> 1613046731.169679: ssid - hexdump_ascii(len=11):
> 41 50 38 34 30 2d 57 50 41 32 33 AP840-WPA23
> 1613046731.169692: proto: 0x2
> 1613046731.169696: Line 9: invalid key_mgmt 'WPA-EAP-SUITE-B-192'
> 1613046731.169699: Line 9: no key_mgmt values configured.
> 1613046731.169701: key_mgmt: 0x0
> 1613046731.169704: Line 9: failed to parse key_mgmt 'WPA-EAP-SUITE-B-
> 1613046731.169708: ieee80211w=2 (0x2)
> The used config was:
> The problem can be solved by adding following two lines to the files in
> This is also breaking the support for these kind of networks in
> Jan Fuchs
> development engineer
> Simon Wunderlich Systementwicklung & Beratung
> Herrenstr. 6, 08523 Plauen, VAT-ID: DE 279397655