Your message dated Mon, 26 Sep 2011 18:38:25 +0200 with message-id <[email protected]> and subject line Re: [pkg-wpa-devel] Bug#504765: wpasupplicant: Only wpa2-psk keys of less than 64 must be quoted has caused the Debian Bug report #504765, regarding wpasupplicant: Only wpa2-psk keys of less than 64 must be quoted to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 504765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504765 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: wpasupplicant Version: 0.6.4-2 Severity: normal Hello, When the WPA2 PSK key is of other length than 64 characters, it needs to be quoted, while 64 char psk-s are ok. Please make the behaviour consistent, either by requiering 64 character keys to be qouted, too, or by allowing the other sizes to be unquoted. For this config I get an error: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 network={ ssid="foo" scan_ssid=1 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP group=CCMP psk=012345678901234567890123456789012345678901234567890123456789012 } Initializing interface 'wlan0' conf '/tmp/wpa.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/tmp/wpa.conf' -> '/tmp/wpa.conf' Reading configuration file '/tmp/wpa.conf' ctrl_interface='/var/run/wpa_supplicant' ctrl_interface_group='0' (DEPRECATED) eapol_version=1 ap_scan=1 Line 13: Invalid PSK '012345678901234567890123456789012345678901234567890123456789012'. Line 13: failed to parse psk '012345678901234567890123456789012345678901234567890123456789012'. Line 14: WPA-PSK accepted for key management, but no PSK configured. Line 14: failed to parse network block. Failed to read or parse configuration '/tmp/wpa.conf'. Failed to add interface wlan0 Cancelling scan request Cancelling authentication timeout But for this I don't: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 network={ ssid="foo" scan_ssid=1 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP group=CCMP psk=0123456789012345678901234567890123456789012345678901234567890123 } Initializing interface 'wlan0' conf '/tmp/wpa.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/tmp/wpa.conf' -> '/tmp/wpa.conf' Reading configuration file '/tmp/wpa.conf' ctrl_interface='/var/run/wpa_supplicant' ctrl_interface_group='0' (DEPRECATED) eapol_version=1 ap_scan=1 Priority group 0 id=0 ssid='foo' Initializing interface (2) 'wlan0' Interface wlan0 set UP - waiting a second for the driver to complete initialization SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf capabilities: key_mgmt 0xf enc 0xf flags 0x0 WEXT: Operstate: linkmode=1, operstate=5 Own MAC address: 00:16:cf:cb:27:2b wpa_driver_wext_set_wpa wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_countermeasures wpa_driver_wext_set_drop_unencrypted RSN: flushing PMKID list in the driver Setting scan request: 0 sec 100000 usec EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED ctrl_interface_group=0 Added interface wlan0 Ignore event for foreign ifindex 3 RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP]) RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP]) Wireless event: cmd=0x8b19 len=16 Received 299 bytes of scan results (1 BSSes) CTRL-EVENT-SCAN-RESULTS Selecting BSS from priority group 0 Also, I don't get any error if I quote like: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 network={ ssid="foo" scan_ssid=1 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP group=CCMP psk="012345678901234567890123456789012345678901234567890123456789012" } -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable'), (10, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages wpasupplicant depends on: ii adduser 3.110 add and remove users and groups ii libc6 2.7-15 GNU C Library: Shared libraries ii libdbus-1-3 1.2.1-4 simple interprocess messaging syst ii libpcsclite1 1.4.102-1 Middleware to access a smart card ii libreadline5 5.2-3 GNU readline and history libraries ii libssl0.9.8 0.9.8g-13 SSL shared libraries ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl <none> (no description available) pn wpagui <none> (no description available) -- no debconf information
--- End Message ---
--- Begin Message ---Hi On Monday 26 September 2011, Kel Modderman wrote: > On Friday 07 November 2008 10:24:08 Eddy Petrișor wrote: > > Package: wpasupplicant > > Version: 0.6.4-2 > > Severity: normal > > > > Hello, > > > > When the WPA2 PSK key is of other length than 64 characters, it needs to > > be quoted, while 64 char psk-s are ok. > > To quote upstream: > # The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e., > # 32 bytes or as an ASCII passphrase (in which case, the real PSK will be > # generated using the passphrase and SSID). ASCII passphrase must be between > # 8 and 63 characters (inclusive). > > The parser recognises quotation marks as something surrounding ascii plaintext > values, while hex values are not quoted. > > > > > > > Please make the behaviour consistent, either by requiering 64 character > > keys to be qouted, too, or by allowing the other sizes to be unquoted. > > It is consistent in my own opinion. [...] wpasupplicant behaves as documented, therefore I fail to see a bug here. While it is generally considered to be a good idea for parsers to be generous against syntax errors, I don't think that would be a good idea for security sensitive configs. Regards Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
