correct group cipher setting

Chuck Tuffli Chuck.Tuffli at dspg.com
Mon Jan 12 13:40:33 EST 2009


The network block shown is the result of the save_config command, not something I entered. The bug report I got was essentially

1) Use WPS to connect to an open network (this works)
2) Use the save_config command to create a wpa_supplicant.conf file for the next connection attempt (this works)
3) Reconnect using the new conf file

#3 fails with a parse error because my patch sets group_cipher to WPA_CIPHER_NONE which write_group() prints out as NONE. The trick here I guess is to set group_cipher to DEFAULT_GROUP in the case of an open network so that write_group() will skip printing out the group entry entirely.

---chuck

-----Original Message-----
From: Dan Williams [mailto:dcbw at redhat.com]
Sent: Mon 1/12/2009 9:18 AM
To: Chuck Tuffli
Cc: hostap at lists.shmoo.com
Subject: Re: correct group cipher setting
 
On Mon, 2009-01-12 at 18:23 +0200, Chuck Tuffli wrote:
> What is the correct value for group cipher (i.e. ssid->group_cipher)
> in the case of an open network (no encryption)? I naively assumed it
> should be WPA_CIPHER_NONE, but if it is, the saved configuration file
> causes an error:

Open networks do not need the pairwise or group keys at all.  Don't even
bother putting them in the network block.

Dan

______________________________________________________________________
DSP Group, Inc. automatically scans all emails and attachments using MessageLabs Email Security System.
_____________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20090112/ac77db36/attachment.htm 


More information about the HostAP mailing list