| commit | 11dfddb23cfa7463c6c2cb5164cf969200dcf650 | [log] [tgz] |
|---|---|---|
| author | Brian Norris <briannorris@chromium.org> | Fri Oct 04 01:36:48 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Sun Oct 13 07:47:12 2019 |
| tree | 930a08caea4f3901c286a29cacd76a59e25b6e1e | |
| parent | 68459cc3d71b3ccaded2577cec611f0e78a9a73f [diff] |
CHROMIUM: scan: don't enable MAC address randomization in associated scans https://chromium-review.googlesource.com/1707244 broke this. We should only be setting this parameter when we're not connecting/connected. This patch was already rejected upstream for pretty much this reason [1], so marking CHROMIUM for now, to fix ourselves up before taking another stab at upstreaming. Also make the 'else if' into a proper 'if', since the features are semi-independent. [1] See http://lists.infradead.org/pipermail/hostap/2019-October/040633.html for some discussion. BUG=chromium:1011217 TEST=network_WiFi_RandomMACAddress TEST=associated + scanning on Scarlet Change-Id: I8ec1bfc2c215f103342f0ca8aab8a6be05a2fff7 Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/hostap/+/1839206 Reviewed-by: Eric Caruso <ejcaruso@chromium.org>