net: enable CRL sets behind a command line flag.

chrome/common/chrome_switches.cc

Index: chrome/common/chrome_switches.cc
diff --git a/chrome/common/chrome_switches.cc b/chrome/common/chrome_switches.cc
index 093fc2cabdb7e9e09bbe0920910fb3911579d72b..7fa8eb4d4add39c80b3816651b75a2e40d0f02a6 100644
--- a/chrome/common/chrome_switches.cc
+++ b/chrome/common/chrome_switches.cc
@@ -428,6 +428,10 @@ const char kEnableCompositeToTexture[]      = "enable-composite-to-texture";
 // exceeded.
 const char kEnableConnectBackupJobs[]       = "enable-connect-backup-jobs";
 
+// Enables establishing revocation information by downloading a set of CRLs

[wtc, 2011/10/21 23:17:31]

Nit: add "certificate" before "revocation".

"performing on-line checks" is not accurate because a properly
implemented crypto library caches the CRLs persistently.  (NSS
doesn't do that yet.)

[agl, 2011/10/24 20:44:27]

Done.
In the Windows implementation (which I've yet to write), we will be using cached
revocation information, just not on-line checks. So I believe that this comment
is accurate.

(Based on discussions with cemp, I believe that this is possible with
CryptoAPI.)

+// rather than performing on-line checks.
+const char kEnableCRLSets[]                 = "enable-crl-sets";
+
 // Enables web developers to create apps for Chrome without using crx packages.
 const char kEnableCrxlessWebApps[]          = "enable-crxless-web-apps";