Wicd use a template (/etc/wicd/encryption/templates) to create file under /var/lib/wicd/configurations. When we setup WPA2 presharedkey, a templates add delimiter ("). These delimiter are not handled by wpa_supplicant. I look on wicd 1.6 and 1.7, same templates Reproducible: Always Steps to Reproduce: 1.Use wicd without template modification 2. 3. Actual Results: Patch proposal to correct templates Expected Results: Wicd create right file for wpa_supplicant
Created attachment 220747 [details] Modify wpa-psk template file Patch file to correct template file
Hi, I'm not a wicd user, but AFAIK (man wpa_supplicant.conf), there are two different syntaxes for WPA's PSKs : psk="acii-passphrase" and psk=the-wpa-psk-computed-from-the-ascii-passphrase-using-wpa_passphrase-utility
(In reply to comment #2) > Hi, > > I'm not a wicd user, but AFAIK (man wpa_supplicant.conf), there are two > different syntaxes for WPA's PSKs : > > psk="acii-passphrase" > and > psk=the-wpa-psk-computed-from-the-ascii-passphrase-using-wpa_passphrase-utility > Hello, Yes, but inside wicd he have WPA2 (passphrase) and WPA2 (presharedkey) He call wpa_passphrase. I look inside a program and he save it into 'string' value (/etc/wicd/wireless.conf).
Upstream says that Gef is correct and the patch is not exactly right. 16:25 < darkside_> can you have a look at http://bugs.gentoo.org/306423 with attached patch 16:25 <+centurion> Title: Gentoo Bug 306423 - net-misc/wicd use bad templates for wpa-psk (at bugs.gentoo.org) 16:27 <+NaCl> um... 16:28 <+NaCl> Gef is right 16:29 <+NaCl> darkside_: from the looks of things, that patch is unnecessary, and the templates are probably named badly. 16:30 < darkside_> ok 16:30 <+NaCl> um... 16:32 <+NaCl> Unless the huge blob of hex is present in quotes in the generated config file, there shouldn't be a problem 16:33 <+NaCl> Otherwise, this may be a problem (that adam7 may have to look at) 16:33 <+NaCl> Also keep in mind that bugs are being ignored. 16:33 <+NaCl> s/ignored/not fixed unless necessary. 16:36 < darkside_> i know that 16:36 < darkside_> i just don't know how to address his issue really 17:03 <+adam7> hi 17:04 <+adam7> NaCl: what's up? 17:04 <+adam7> NaCl: I think it's possible we need a third WPA template 17:05 <+adam7> ie, for already known psks 17:06 <+adam7> none of the current templates let you enter the hex key if you already know what it is 17:06 <+adam7> in fact, I wonder if the two templates are actually different... 18:23 <+NaCl> adam7: different by the quotes 19:24 <+adam7> NaCl: hm? 19:24 <+adam7> NaCl: yes, I know 19:24 <+adam7> but I think that the end result is the same, actually 19:25 <+NaCl> :/ 19:26 <+adam7> yeah, have to look into that 19:27 <+adam7> but not now
Is there any news about this bug, I can confirm that I can't log into wpa-psk network settled up with hostapd while from windows can.!
(In reply to comment #4) Gef is right of course, but I also confirm something is wrong with the templates. I actually know ONLY the HEX key (I forgot the actual passphrase I chose years ago and the HEX key is the only thing I have). Whatever way I choose to enter the key in wicd GUI, quotes are added as if it was the ascii string. I've add to edit the templates to get a successful connection using wicd. I changed enctype from wpa-psk to wpa, removed the quotes around the psk, and made sure it was called psk and not apsk.
assigning to new maintainer.
Suggestion: I will let the ebuild install the patched version of the wpa_psk template as wpa_apsk. Objections?
(In reply to comment #8) > Suggestion: > I will let the ebuild install the patched version of the wpa_psk template as > wpa_apsk. > Objections? The wpa-psk-hex template is now installed. Thank you for your patience. +*wicd-1.7.1_beta2-r6 (13 Sep 2011) + + 13 Sep 2011; Thomas Kahle <tomka@gentoo.org> -wicd-1.7.1_beta2-r5.ebuild, + +wicd-1.7.1_beta2-r6.ebuild, +files/add-wpa-psk-hex-template.patch, + +files/fix-ad-hoc-networking.patch: + Fix bugs 351337 (ad-hoc-net), 306423 (wpa-hex-template)
