As part of preparation for LTE activation (which can be done through a captive portal), chromeos::MobileActivator disables kCertRevocationCheckingEnabled pref in local state.
This has no effect any more given that ability for users to check this pref was removed some time ago: https://crbug.com/361820
The pref value is ignored, with cert revocation checks disabled by default, unless it's set by a policy. If the cert revocation is set by policy, that value will override pref value set at user level, so setting the value in chromeos::MobileActivator will have no effect either.
In short, kCertRevocationCheckingEnabled handling in chromeos::MobileActivator should be safe to remove.
Comment 1 by bugdroid1@chromium.org
, Dec 4