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:
Created attachment 5824 [details] /etc/wpa_supplicant.conf bugged file It is the interesting part created by drakxtools.
This seems simple to fix, it is a one liner for a perl guru like tv ;-)
CC: (none) => thierry.vignaudAssignee: bugsquad => mageia
Severity: major => normalSummary: Drakxtools allow too long WEP keys => Drakconnect allows too long WEP keysSource RPM: drakxtools => drakx-net
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/
This seems simple to fix, it is a one liner for a perl guru, which file should I look at?
Version: 4 => 5
@ 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) => marja11Assignee: mageia => mageiatools
Whiteboard: (none) => MGA6TOOVersion: 5 => Cauldron
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
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 => MGA8TOOCC: (none) => yves.brungard_mageia