commit | 11c224b7054a3f0dc5a34c2903e13f74376db27e | [log] [tgz] |
---|---|---|
author | Paul Stewart <pstew@chromium.org> | Tue Oct 22 19:04:40 2013 -0700 |
committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | Fri Oct 25 03:10:08 2013 +0000 |
tree | 170c53cb451dbb34acb11b42b3c626c209ea7e00 | |
parent | 75a68b9f230c7715cc24feee8a713e75e6e7f231 [diff] |
shill: WiFi: Provide wpa_supplicant a PIN if asked for There are conditions under which wpa_supplicant will clear the "pin" property of its configuration, even if this was previously supplied by shill. Under these circumstances it wil request it again as the EAP negotiation starts. This change provides the means for the WiFi object to detect when this parameter is being requested and to supply this value to wpa_supplicant if the WiFiService has this information on hand. BUG=chromium:310296 TEST=Unit tests + new autotest: https://chromium-review.googlesource.com/174170 This autotest still fails the following but shows in the supplicant logs: CTRL_IFACE: response handle field=PIN EAPOL: received control response (user input) notification - retrying pending EAP Request indicating that the PIN has been successfully provided to wpa_supplicant Change-Id: I91bc3ddd01a335f93d20cca4d47ca497bd631ebe Reviewed-on: https://chromium-review.googlesource.com/174180 Reviewed-by: mukesh agrawal <quiche@chromium.org> Commit-Queue: Paul Stewart <pstew@chromium.org> Tested-by: Paul Stewart <pstew@chromium.org>