Hi, On Fri, 12 Feb 2021, at 09:58, Sven Eckelmann wrote: > Control: tags -1 - wontfix > Control: reopen -1 > > On Fri, 12 Feb 2021 09:14:56 +0100 "Andrej Shadura" <and...@shadura.me> wrote: > > Control: tag -1 wontfix > > Control: fixed -1 2:2.6-4 > [...] > > The version specified the first version where the problem was found. The > problem was not fixed since then. Just tested it here with wpasupplicant > 2:2.9.0-16.
As I was not aware of this, what I did at that moment was right. My understanding is that this option has been enabled by default since 2.5 upstream. I’m not sure why it fails for you. > Line 6: invalid key_mgmt 'WPA-EAP-SUITE-B-192' > Line 6: no key_mgmt values configured. > Line 6: failed to parse key_mgmt 'WPA-EAP-SUITE-B-192'. > Line 17: failed to parse network block. > > So I've just reopened the bug. And all affected versions are shown in this > nice graph in the bug ticket. So as you you can see, the provided info > even helps you to figure out what is affected - even when you will most > likely > fix only the problem for unstable. -- Cheers, Andrej
