flimflam: dbus: Set correct values for PAP/CHAP with TTLS
These settings better match how wpa_supplicant uses EAP-TTLS
for PAP and CHAP. The "autheap=" parameter only works for
EAP types that are available at the top-level EAP capabilities,
and refer to a tunneled EAP transaction (as opposed to a raw
protocol tunneled within TLS).
Notably, this change reassigns the purpose of the "MSCHAPv2"
functionality in the Chrome 802.1x dialog from EAP-TTLS/EAP-MSCHAPv2
to EAP-TTLS/MSCHAPv2. On the minus side this may change current
configurations. On the plus side it enables users who were previously
unable to reach MSCHAPv2 in any way through the UI. EAP-MSCHAPv2 users
can still operate using the "auto" option. For the others (MSCHAP,
CHAP, and PAP) those parameters never made sense and didn't map to
anything in the supplicant.
I have opened crosbug.com/26822 to have the EAP-MSCHAPv2 surface as a
separate user-selectable option in the UI.
BUG=chromium-os:26638
TEST=Manual: Tested that each of the "auth=" parameters listed here
mapped to the correct transformation. Writing new autotests as
well for these authenticators. New autotest in
https://gerrit.chromium.org/gerrit/16557
Change-Id: Ie3034eeeb5ffb61ccd9f2647e5c9d29c83735ca9
(cherry picked from commit a6296f4fa31653fa48c437e3d04d05d7d3c1f55d)
1 file changed
