[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 20 Sep 2021 21:18:19 UTC

Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> changed:

           What    |Removed                     |Added
           Severity|Affects Some People         |Affects Only Me

--- Comment #16 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> ---
We should all take it easy, it is a minor breakage and probably no other setups
except mine are affected. On the other hand, the security/wpa_supplicant from
ports still works as intended.

The QA process takes some time, the same for debugging and writing patches, but
also taking dumps and testing patches requires some time and effort including
either driving tens of miles or recreating EAP/PEAP secured network in the home

I have no insight into @freebsd.org e-mail server setup, but believe it does
some false positives marking messages as SPAM what makes writing direct email
messages a bit hopeless.

The first conclusion: "no other setups are probably affected" is pretty sad and
means that FreeBSD's user base became FreeBSD's consumer base. I have reported
this breakage a week or two ago on the net@ mailing list and there was no
feedback at all. The FreeBSD consumer base utilizes probably only RELEASEs and
cares neither for the development process nor for the quality of the upcoming

The final question which comes here is: Do we really need wpa_supplicant in the
base? I was against ftpd(8) removal which IMHO is an imminent part of the
FreeBSD OS, but wpa_supplicant can be easily installed from ports. Consumers
who have only WiFi access can have the package on the USB stick.

Kind regards, 
FreeBSD User

You are receiving this mail because:
You are on the CC list for the bug.