FS#62253 - RFE: Provide wpa_supplicant 2.7

Attached to Project: Arch Linux
Opened by Andrew (abrouwers) - Saturday, 06 April 2019, 10:38 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 20 July 2019, 17:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
This package has had a pretty ugly past, but just about all major distributions have made the wpa_supplicant-2.7 + openssl-1.1 migration - including SLACKWARE! Please give this some love, even if it's to [testing].

Debian: https://packages.debian.org/buster/wpasupplicant
Fedora: https://src.fedoraproject.org/rpms/wpa_supplicant/blob/master/f/wpa_supplicant.spec#_9
Slackware: ftp://ftp.osuosl.org/pub/slackware/slackware64-current/source/n/wpa_supplicant/

...etc.
This task depends upon

Closed by  Antonio Rojas (arojas)
Saturday, 20 July 2019, 17:09 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Saturday, 06 April 2019, 14:35 GMT
See https://bbs.archlinux.org/viewtopic.php?id=244079 /  FS#61119  for 2.7 if you could confirm the fixes for brcmfmac or work with upstream on the wl driver that would be great
See  FS#54390  for openssl 1.1
Comment by Andrew (abrouwers) - Saturday, 06 April 2019, 15:01 GMT
Very interesting links, thanks. I don't have such hardware, so can't confirm. It's quite strange that arch is being so much more conservative than eg. debian.
Comment by Chih-Hsuan Yen (yan12125) - Sunday, 07 April 2019, 10:13 GMT
Just tried wpa_supplicant 2.7 from https://git.archlinux.org/svntogit/packages.git/tree/trunk?id=a7264940a4217eabbb05b123c8d741697eaaf744. It's still broken as described in  FS#61119 . Tested an unencrypted public Wi-Fi service using the broadcom-wl driver for BCM4360 on MacBookAir7,2.

By the way, git-master of wpa_supplicant works with the same network adapter.
Comment by loqs (loqs) - Sunday, 07 April 2019, 10:23 GMT
@yan12125 if you remove CONFIG_FILS=y from config a7264940a4217eabbb05b123c8d741697eaaf744 should then work with broadcom-wl.
Edit:
Was git-master working with CONFIG_FILS=y using broadcom-wl?
Comment by Chih-Hsuan Yen (yan12125) - Monday, 08 April 2019, 04:48 GMT
> Was git-master working with CONFIG_FILS=y using broadcom-wl?

Yes!

> if you remove CONFIG_FILS=y from config a7264940a4217eabbb05b123c8d741697eaaf744 should then work with broadcom-wl.

Too lazy to try it out as git-master already works fine :)
Comment by loqs (loqs) - Tuesday, 09 April 2019, 00:19 GMT
@yan12125 locally the issue is still present with CONFIG_FILS=y as of commit 6bb9d9a8db899278032eac6e7df7d7b999a9956e
Comment by Chih-Hsuan Yen (yan12125) - Wednesday, 10 April 2019, 11:10 GMT
Sorry I forgot my local build also includes CONFIG_OWE=y. I did more testing for various scenarios and here are results:

OpenSSL 1.1 + CONFIG_OWE + wpa_supplicant git-master: working
OpenSSL 1.0 + CONFIG_OWE + wpa_supplicant git-master: working
OpenSSL 1.1 + wpa_supplicant git-master: not working
OpenSSL 1.0 + wpa_supplicant git-master: not working
OpenSSL 1.0 + wpa_supplicant 2.7: not working
OpenSSL 1.0 + CONFIG_OWE + wpa_supplicant 2.7: not working

There's still a bug in wpa_supplicant git-master, apparently.
Comment by loqs (loqs) - Tuesday, 30 April 2019, 19:09 GMT
wpa_supplicant 2:2.8-1 is now in testing [1]

[1] https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/wpa_supplicant&id=313ed4fee0501a4d9f21c1173137904f7737f0a9

Loading...