From 6fb3737263c52d749295ed7c3172fa478df1ca4d Mon Sep 17 00:00:00 2001
From: Raymond Hill <gorhill@users.noreply.github.com>
Date: Mon, 1 Jun 2015 17:10:38 -0400
Subject: [PATCH] Updated About the required permissions (markdown)

---
 About-the-required-permissions.md | 35 +++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)

diff --git a/About-the-required-permissions.md b/About-the-required-permissions.md
index bb022ae..d8e9a88 100644
--- a/About-the-required-permissions.md
+++ b/About-the-required-permissions.md
@@ -1,3 +1,38 @@
+### Some insights into uBlock's required (Chromium) permissions
+
+uBlock's required permissions are the same as those of Privacy Badger, except that Privacy Badger requires one extra permission, `cookies`. This is  uBlock's required permissions:
+
+    "permissions": [
+        "contextMenus",
+        "privacy",
+        "storage",
+        "tabs",
+        "unlimitedStorage",
+        "webNavigation",
+        "webRequest",
+        "webRequestBlocking",
+        "http://*/*",
+        "https://*/*"
+    ],
+
+This is Privacy Badger required permissions:
+
+    "permissions": [
+        "contextMenus",
+        "cookies",
+        "privacy",
+        "storage",
+        "tabs",
+        "unlimitedStorage",
+        "webNavigation",
+        "webRequest",
+        "webRequestBlocking",
+        "http://*/*",
+        "https://*/*"
+    ],
+
+It should come as no surprise that privacy-minded extensions require the `privacy` permission.
+
 ### "Access your data on all web sites"
 
 Since [first version](https://github.com/gorhill/uBlock/blob/b5fdac90539b19a0db8f36ea537bd150edb4d9c8/manifest.json).