Bug 25721 - SSID names with hex bytes handled inconsistantly between the programs resulting in no connectivity
Summary: SSID names with hex bytes handled inconsistantly between the programs resulti...
Status: RESOLVED DUPLICATE of bug 25720
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-21 21:52 CET by w unruh
Modified: 2019-11-22 03:59 CET (History)
0 users

See Also:
Source RPM: Network center and wpa_supplicant and iwlist
CVE:
Status comment:


Attachments

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
A duplicate entry due to bug in bug tracker

*** This bug has been marked as a duplicate of bug 25720 ***

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


Note You need to log in before you can comment on or make changes to this bug.