modified allowlist readme in chrome

This commit is contained in:
Amit Nandi 2025-04-05 01:46:09 +05:30
parent 02a58b0262
commit a637e3797b
2 changed files with 67 additions and 84 deletions

View file

@ -1,66 +0,0 @@
<!DOCTYPE html []>
<html>
<head>
<meta charset="UTF-8" />
<meta name="author" content="MarkdownViewer++" />
<title>README.md</title>
<style type="text/css">
/* Avoid page breaks inside the most common attributes, especially for exports (i.e. PDF) */
td, h1, h2, h3, h4, h5, p, ul, ol, li {
page-break-inside: avoid;
}
</style>
</head>
<body>
<h1 id="add-extension-crx-to-allowlist">Add extension (crx) to allowlist</h1>
<ul>
<li>
<a href="#windows">Windows</a>
</li>
<li>
<a href="#macOS">macOS</a>
</li>
<li>
<a href="#linux">Linux</a>
</li>
</ul>
<h3 id="windows">Windows</h3>
<p>Advance Notice: after adding the allowlist-policy you'll get a message <em>Your browser is managed by your organisation</em> on the extensions page (and some settings like Secure DNS are disabled).<br />
To remove this message you'll have to remove the added policy from the registry again (run regedit and for Chrome check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome).</p>
<p>If you still want to add the extension to the allowlist:</p>
<p>Run as administrator one of the reg-files in allowlist-folder of extension (unzip).</p>
<ul>
<li>for Edge 116+ you may also need to run the <em>Forcelist</em> reg-file (also undo reg-file provided) or switch to <em>Load unpacked</em> installation.</li>
</ul>
<p>If you already added extensions to the allowlist than you should change "1" to a new value (also change name of HLM-key for beta/developer versions of browsers).<br />
To add more extensions to the allowlist you can add more lines.<br />
Example Chrome-regfile:</p>
<pre>
<code>Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist]
"1"="lkbebcjgcmobigpeffafkodonchffocl"
"2"="extension-id2"
</code>
</pre>
<p>You can also run the PowerShell script <em>bypass_paywalls_clean_allowlist.ps1</em> (as administrator) to add extension to the allowlist (script checks if extension already allowed or adds new registry-key).<br />
For the parameter browser enter chrome, edge or brave.</p>
<h3 id="macos">macOS</h3>
<p>Run with admin rights one of the .mobileconfig files in allowlist-folder of extension (unzip).<br />
Finally restart the browser's process (in the Dock: right click on Chrome, 'Quit', reopen).<br />
This assumes your device is not being managed by MDM software and you don't have any profile related to the 'ExtensionInstallAllowlist' policy already active.<br />
To add more extensions to the allowlist you can add more lines.</p>
<pre>
<code>&lt;key&gt;ExtensionInstallAllowlist&lt;/key&gt;
&lt;array&gt;
&lt;string&gt;lkbebcjgcmobigpeffafkodonchffocl&lt;/string&gt;
&lt;string&gt;extension-id2&lt;/string&gt;
&lt;/array&gt;
</code>
</pre>
<h3 id="linux">Linux</h3>
<p>
<a href="https://developer.chrome.com/docs/extensions/mv3/hosting/#hosting">Chromium-based browsers allow local installations of extensions</a>, so not necessary :)</p>
</body>
</html>

View file

@ -1,46 +1,95 @@
# Add extension (crx) to allowlist # Add extension (crx) to allowlist
* [Windows](#windows) * [Windows](#windows)
* [macOS](#macOS) * [macOS](#macOS)
* [Linux](#linux) * [Linux](#linux)
### Windows ### Windows
Advance Notice: after adding the allowlist-policy you'll get a message *Your browser is managed by your organisation* on the extensions page (and some settings like Secure DNS are disabled).\
To remove this message you'll have to remove the added policy from the registry again (run regedit and for Chrome check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome).
> Advance Notice: after adding the allowlist-policy you'll get a message
> *Your browser is managed by your organisation* on the extensions page (and some settings like Secure DNS are disabled).
>
> To remove this message you'll have to remove the added policy from the
> registry again (run regedit and for Chrome check
> HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome).
If you still want to add the extension to the allowlist: If you still want to add the extension to the allowlist:
Run as administrator one of the reg-files in allowlist-folder of extension (unzip).
* for Edge 116+ you may also need to run the *Forcelist* reg-file (also undo reg-file provided) or switch to *Load unpacked* installation.
- Run as administrator one of the reg-files in allowlist-folder of [this](https://forge.bitmutex.com/bitmutex/bpc/archive/chrome.zip) repo-branch (unzip).
- for Edge 116+ you may also need to run the `Forcelist` reg-file (also undo reg-file provided) or switch to *Load unpacked* installation.
- If you already added extensions to the allowlist than you should change "1" to a new value (also change name of HLM-key for beta/developer versions of browsers).
- To add more extensions to the allowlist you can add more lines.
If you already added extensions to the allowlist than you should change "1" to a new value (also change name of HLM-key for beta/developer versions of browsers).\
To add more extensions to the allowlist you can add more lines.\
Example Chrome-regfile: Example Chrome-regfile:
```
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist]
"1"="lkbebcjgcmobigpeffafkodonchffocl"
"2"="extension-id2"
``` ```
You can also run the PowerShell script *bypass_paywalls_clean_allowlist.ps1* (as administrator) to add extension to the allowlist (script checks if extension already allowed or adds new registry-key).\ Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist]
"1"="lkbebcjgcmobigpeffafkodonchffocl"
"2"="extension-id2"
```
You can also run the PowerShell script `bypass_paywalls_clean_allowlist.ps1` (as administrator) to add extension to the allowlist (script checks if extension already allowed or adds new registry-key).\
For the parameter browser enter chrome, edge or brave. For the parameter browser enter chrome, edge or brave.
### macOS ### macOS
Run with admin rights one of the .mobileconfig files in allowlist-folder of extension (unzip).\
Finally restart the browser's process (in the Dock: right click on Chrome, 'Quit', reopen).\
This assumes your device is not being managed by MDM software and you don't have any profile related to the 'ExtensionInstallAllowlist' policy already active.\ - Run with admin rights one of the .mobileconfig files in allowlist-folder of extension (unzip).
To add more extensions to the allowlist you can add more lines.
``` - Finally restart the browser's process (in the Dock: right click on Chrome, 'Quit', reopen).
- This assumes your device is not being managed by MDM software and you don't have any profile related to the 'ExtensionInstallAllowlist' policy already active.\
- To add more extensions to the allowlist you can add more lines.
``` xml
<key>ExtensionInstallAllowlist</key> <key>ExtensionInstallAllowlist</key>
<array> <array>
<string>lkbebcjgcmobigpeffafkodonchffocl</string> <string>lkbebcjgcmobigpeffafkodonchffocl</string>
<string>extension-id2</string> <string>extension-id2</string>
</array> </array>
``` ```
### Linux ### Linux
[Chromium-based browsers allow local installations of extensions](https://developer.chrome.com/docs/extensions/mv3/hosting/#hosting), so not necessary :)
[Chromium-based browsers allow local installations of extensions](https://developer.chrome.com/docs/extensions/mv3/hosting/#hosting), so not necessary :)