Block NPAPI plugins by default Add Facebook video calling and Google Earth plugins to the tracked l…

chrome/browser/plugins/plugin_metadata.cc

Index: chrome/browser/plugins/plugin_metadata.cc
diff --git a/chrome/browser/plugins/plugin_metadata.cc b/chrome/browser/plugins/plugin_metadata.cc
index 5f2fc50ba2748a73ebd8bf3296d1fb7b73cde83d..5f40e06c0a89e79aa34ede5953958147909f7d63 100644
--- a/chrome/browser/plugins/plugin_metadata.cc
+++ b/chrome/browser/plugins/plugin_metadata.cc
@@ -94,9 +94,13 @@ PluginMetadata::SecurityStatus PluginMetadata::GetSecurityStatus(
     const content::WebPluginInfo& plugin) const {
   if (versions_.empty()) {
 #if defined(OS_LINUX)
-    // On Linux, unknown plugins require authorization.
+    // On Linux, unknown plugins require authorization.
     return SECURITY_STATUS_REQUIRES_AUTHORIZATION;
 #else
+    if (plugin.type == content::WebPluginInfo::PLUGIN_TYPE_NPAPI) {

[Bernhard Bauer, 2013/09/24 18:16:56]

This check isn't necessary. Pepper plug-ins are already exempted from
infobarring
(https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/plu...).

[Cris Neckar, 2013/09/24 18:52:00]

Done.

+      // Unknown NPAPI plugins require authorization.
+      return SECURITY_STATUS_REQUIRES_AUTHORIZATION;
+    }
     return SECURITY_STATUS_UP_TO_DATE;
 #endif
   }