Add nativeMessaging extension permission

chrome/common/extensions/permissions/api_permission.cc

Index: chrome/common/extensions/permissions/api_permission.cc
diff --git a/chrome/common/extensions/permissions/api_permission.cc b/chrome/common/extensions/permissions/api_permission.cc
index 818e80129e5b9a317d04727a19fe4840e8cf228b..8737f1000a78bda29308679e537a4ffd1e2d88f9 100644
--- a/chrome/common/extensions/permissions/api_permission.cc
+++ b/chrome/common/extensions/permissions/api_permission.cc
@@ -218,6 +218,9 @@ void APIPermissionInfo::RegisterAllPermissions(
     { APIPermission::kManagement, "management", kFlagNone,
       IDS_EXTENSION_PROMPT_WARNING_MANAGEMENT,
       PermissionMessage::kManagement },
+    { APIPermission::kNativeMessaging, "nativeMessaging", kFlagNone,
+      IDS_EXTENSION_PROMPT_NATIVE_MESSAGING,
+      PermissionMessage::kNativeMessaging },

[Matt Perry, 2013/03/02 00:33:54]

Let's copy the entry for APIPermission::kPlugin since it gives effectively the
same level of access. Use the same warning message as well.

[Sergey Ulanov, 2013/03/02 01:14:27]

Not sure it's the same level of access: Native messaging is allowed only when
the native host is already installed on the machine and it allows connections
from that particular extension.

     { APIPermission::kPrivacy, "privacy", kFlagNone,
       IDS_EXTENSION_PROMPT_WARNING_PRIVACY,
       PermissionMessage::kPrivacy },