Chrome Version: 60.0.3112.114 (Official Build) (64-bit)
Chrome OS Version: 9592.96.0 (Official Build) stable-channel
Chrome OS Platform: samus

Steps To Reproduce:
With a US Chromebook outside the US, try to associate with a channel 12-14 AP before associating with any other AP.

Expected Result:
The channel 12-14 network is visible, and can be used.

Actual Result:
The Chromebook forbids even passive scanning on channels 12-14.

What is the impact to the user, and is there a workaround? If so, what is
it?
Associating with a channel 1-11 AP that provides country information first allows associating with all allowed channels afterward.



- cfg80211 already ensures regulatory compliance by defaulting to CRDA country 00, which is maximally restrictive while still allowing passive scanning for other channels.
- /lib/udev/rules.d/85-regulatory.rules already causes the regulatory domain to be set appropriately on AP association.

This means that /etc/init/regulatory-domain.conf is both unnecessary harmful: Setting the regulatory domain from the VPD region means that Chrome OS devices might be non-compliant (!!) outside of that region until they associate with an AP.

Maybe storm and gale can set theirs from their WAN IP? The default of 00 is safe in any case.