[PATCH] Allow more psk/psk2 and tkip/aes wireless configurations
|Reported by:||wberrier@…||Owned by:||developers|
|Keywords:||nas wpa wpa2 tkip aes psk psk2||Cc:|
Based on #4687 , but I didn't have permissions to open that ticket, so I'm posting a new one here.
Based on the recent tkip/wpa vulnerabilities, it would be nice to have more fine grained control over how the wireless is set up. This allows me to secure the network, but still allow older clients/drivers to connect.
This is a fix based from here:
And allows the following combinations:
auth,wsec table (implemented in broadcom.sh):
4,2: psk/tkip 4,4: psk/aes 4,6: psk/tkip+aes (currently unsupported) 128,2: psk2/tkip (currently unsupported) 128,4: psk2/aes 128,6: psk2/tkip+aes (currently unsupported) 132,2: psk+psk2/tkip (currently unsupported) 132,4: psk+psk2/aes (currently unsupported) 132,6: psk+psk2/tkip+aes ------------------ 2,2: wpa/tkip 2,4: wpa/aes (currently unsupported) 2,6: wpa/tkip+aes (currently unsupported) 64,2: wpa2/tkip (currently unsupported) 64,4: wpa2/aes 64,6: wpa2/tkip+aes (currently unsupported) 66,2: wpa+wpa2/tkip (currently unsupported) 66,4: wpa+wpa2/aes (currently unsupported) 66,6: wpa+wpa2/tkip+aes
Note, you'll have to use quotes around the config option if you want to use a pipe:
option encryption "psk+psk2|aes"
or, you can use a different char, such as a colon without quotes:
option encryption psk+psk2:aes
Change History (6)
Changed 8 years ago by wberrier@…
comment:1 Changed 7 years ago by nico
- Milestone changed from Kamikaze 8.09.2 to Kamikaze Features Paradize
- Version changed from Kamikaze 8.09 to Trunk