Bug 11186

Summary:	wpa_supplicant dies on any config error in any block in wpa_supplicant.conf
Product:	Mageia	Reporter:	w unruh <unruh>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal
Version:	2
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	wpa_supplicant	CVE:
Status comment:

Description w unruh 2013-09-06 17:09:09 CEST

Description of problem:
wpa_supplicant dies if any error found in any of the network blocks, making it ans wireless useless.

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:
Mageia produced a wpa_supplicant.conf with an empty psk line
psk=
wpa_supplicant found this to be invalid and refused to continue to parse the file, making wireless cease working.
The parsing of the wpa_supplicant.conf file is broken.
wpa_supplicant then refused to use any of the
succeeding network blocks in the file. The network I was attempting to attach
to had a different essid than the corrupt block, and was entered correctly into
wpa_supplicant file, but wpa_supplicant refused to use it, claiming it was
unable to parse the file. It had managed to parse the file just before because
it listed all of the essid of the network blocks in the wpa_supplicant.conf
file.
It took me two months, and inability to use wireless on three trips, to find
the problem.

Once I removed the corrupt block everything worked fine.
This has apparently been fixed in wpa_supplicant 1.0 and higher. To quote
from the wpa_supplicant bugs list

"This bug looks fixed to me. If you add "WPA_IGNORE_CONFIG_ERRORS" CFLAG to the
configuration file during build..then the bad network blocks are skipped.This
change was made in V1.0 of wpa_supplicant."

This needs to be implimented in Mageia 2 (and perhaps mageia 3 as well. I do not run it, so cannot see if Mageia has implemented that flag in the compilation.

Reproducible:

Steps to Reproduce:

Comment 1 Manuel Hiebel 2013-10-22 12:21:03 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 2 Manuel Hiebel 2013-11-23 16:16:33 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD