Bug 116083 - wpa_supplicant can't deal with dash-separated hex keys
Summary: wpa_supplicant can't deal with dash-separated hex keys
Status: VERIFIED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: RC 1
Hardware: Other All
: P5 - None : Major
Target Milestone: ---
Assignee: Joachim Gleissner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-09 10:23 UTC by Reinhard Max
Modified: 2007-06-05 10:04 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Suggested patch (228 bytes, patch)
2005-09-09 10:39 UTC, Reinhard Max 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Reinhard Max 2005-09-09 10:23:00 UTC 
YaST online-help suggests using dashes to split hex keys for WEP and WPA into
groups of four digits, but when starting a wireless interface that was
configured that way, wpa_supplicant complains about the key having an invalid
format, and exits, leaving the device in an unusable state.

So either wpa-supplicant should be changed to accept dash-separated keys, or the
network initialisation scripts should remove the dashes from hex keys, when
generating the config file for wpa_supplicant.
Comment 1 Joachim Gleissner 2005-09-09 10:38:17 UTC 
Fixed package submitted.
Comment 2 Reinhard Max 2005-09-09 10:39:42 UTC 
Created attachment 49355 [details]
Suggested patch

It removes everything that is not a hex digit from the key when generating the
wpa_supplicant config file.