Bug 15076 - Drakconnect allows too long WEP keys
Summary: Drakconnect allows too long WEP keys
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard: MGA8TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-18 10:56 CET by José Jorge
Modified: 2021-09-07 19:10 CEST (History)
4 users (show)

See Also:
Source RPM: drakx-net
CVE:
Status comment:


Attachments
/etc/wpa_supplicant.conf bugged file (191 bytes, text/plain)
2015-01-18 11:01 CET, José Jorge
Details

Description José Jorge 2015-01-18 10:56:02 CET
Description of problem:
If a user writes  a too long WEP key, wpa_supplicant process fails silently, the user just sees he cannot connect to Wifi anymore.

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

How reproducible:
always

Steps to Reproduce:
Either try to connect from net_applet to a WEP network entering a long key as "bruno.chaumette@libertysurf.fr" or use the attached wpa conf file with : 

wpa_supplicant -iwlan0 -c wpa_supplicant.conf

Successfully initialized wpa_supplicant
Line 13: Too long WEP key 0 '"bruno.chaumette@libertysurf.fr"'.
Line 13: failed to parse wep_key0 '"bruno.chaumette@libertysurf.fr"'.
Line 18: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.

Reproducible: 

Steps to Reproduce:
Comment 1 José Jorge 2015-01-18 11:01:13 CET
Created attachment 5824 [details]
/etc/wpa_supplicant.conf bugged file

It is the interesting part created by drakxtools.
Comment 2 José Jorge 2015-01-18 11:02:18 CET
This seems simple to fix, it is a one liner for a perl guru like tv ;-)
David Walser 2015-01-18 19:16:41 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => mageia

Thierry Vignaud 2015-05-19 10:07:32 CEST

Severity: major => normal
Summary: Drakxtools allow too long WEP keys => Drakconnect allows too long WEP keys
Source RPM: drakxtools => drakx-net

Comment 3 Samuel Verschelde 2015-09-21 13:19:38 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 José Jorge 2015-10-25 12:13:18 CET
This seems simple to fix, it is a one liner for a perl guru, which file should I look at?

Version: 4 => 5

Comment 5 Marja Van Waes 2018-04-14 23:59:08 CEST
@ José,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11
Assignee: mageia => mageiatools

José Jorge 2018-04-15 08:11:22 CEST

Whiteboard: (none) => MGA6TOO
Version: 5 => Cauldron

Comment 6 Dave Hodgins 2018-04-15 08:50:50 CEST
Note that the length limit varies depending on the type of wep used.
From https://www.lifewire.com/what-is-a-wep-key-818305
40- or 64-bit WEP: 10 digit key
104- or 128-bit WEP: 26 digit key
256-bit WEP: 58 digit key

CC: (none) => davidwhodgins

Comment 7 papoteur 2021-09-07 19:10:01 CEST
I got the same error.
However my wifi connection is configured to be WPA(PSK).
Why does it say that the key is WEP?

Whiteboard: MGA6TOO => MGA8TOO
CC: (none) => yves.brungard_mageia


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