Bug 25720

Summary:	SSID names with hex bytes handled inconsistantly between the programs resulting in no connectivity
Product:	Mageia	Reporter:	w unruh <unruh>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	thierry.vignaud
Version:	7
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	wpa_supplicant-2.9-1.1.mga7.src.rpm	CVE:
Status comment:

Description w unruh 2019-11-21 21:52:10 CET

Description of problem:
I just ran across a problem at the Univ Para in Belem Brazil One of their SSID has (I presume) UTF code in the name. but Network center, iwlist, and wpa_supplicant treat the name differently-- in particular some Capitalize the hex bytes and others do not. Also Network center does not treat the ssid properly.
The SSID is
ppgf_audit\xc3\xe3io_LPF Unfortunately something reports this as 
ppgf_audit\xC3\xE3io_LPF which of course does not match the other one. 

In addition, the wpa_supplicant name in /etc/wpa_supplicant.conf as
ssid="ppgf_audit\xc3\xe3io_LPF" but the "string version" (in double qoutes does not translate into the appropriate bytes. It should be
ssid=P"ppgf_audit\xc3\xe3io_LPF" so that wpa_supplicant treats the escape sequences properly. (in fact there is no reason why the ssid=P"..." form should not be used for all the ssid= lines in wpa_supplicant.conf).

The short problemis that wpasupplicant refuses to connect to such an ssid, since the match strings do NOT agree.


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

2.9-1.1  wpa_supplicant
wireless-tools-30-0.pre9.11.mga7
libdrakx-net-2.42-1.mga7

How reproducible: Always

Steps to Reproduce: Try to use NetworkCenter to connect to an SSID with escape characters in it.

Comment 1 w unruh 2019-11-22 03:59:45 CET

*** Bug 25721 has been marked as a duplicate of this bug. ***

Comment 2 Lewis Smith 2019-11-22 13:54:16 CET

*** Bug 25722 has been marked as a duplicate of this bug. ***

Comment 3 Lewis Smith 2019-11-22 18:14:08 CET

*** Bug 25719 has been marked as a duplicate of this bug. ***

Comment 4 Lewis Smith 2019-11-22 18:17:00 CET

Thank you w unruh for pointing out this problem (just once would have helped).
This is one of 4 equal bugs, the only one to treat.

Assigning to registered maintainer tmb for:
 wpa_supplicant-2.9-1.1.mga7.src.rpm
 wireless-tools-30-0.pre9.11.mga7.src.rpm
CC tv for:
 drakx-net-2.42-1.mga7.src.rpm

Source RPM: Network center and wpa_supplicant and iwlist => wpa_supplicant-2.9-1.1.mga7.src.rpm
Assignee: bugsquad => tmb
CC: (none) => thierry.vignaud

Comment 5 w unruh 2019-12-13 22:19:28 CET

I do appologise. The bugs web page kept indicating that the attempt to post had crashed and failed, so I tried again, and again. Sorry.

Comment 6 Lewis Smith 2019-12-14 21:17:15 CET

See also bug 25871.

Comment 7 Aurelien Oudelet 2021-07-06 13:14:24 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 8 Marja Van Waes 2021-09-07 14:10:57 CEST

Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

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