{"id":26307,"date":"2022-08-29T01:33:49","date_gmt":"2022-08-28T23:33:49","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=26307"},"modified":"2022-08-29T01:33:49","modified_gmt":"2022-08-28T23:33:49","slug":"google-chrome-blockliste-fr-erweiterungen-admx-in-build-86-gendert","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/08\/29\/google-chrome-blockliste-fr-erweiterungen-admx-in-build-86-gendert\/","title":{"rendered":"Google Chrome: Block list for extensions (ADMX) has changed in build 86"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2021\/06\/Chrome-01.jpg\">[<a href=\"https:\/\/www.borncity.com\/blog\/2022\/08\/29\/google-chrome-blockliste-fr-erweiterungen-admx-in-build-86-gendert\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]Small information\/reminder for administrators who use Google Chrome in corporate environments on Windows and manage the installation of Chrome Extensions by users via group policies. As of Chrome 86, the naming of a policy has changed &#8211; those who have not considered the ADMX entries in question are walking into a trap &#8211; users can install arbitrary extensions in Chrome.<!--more--><\/p>\n<h2>Block list Chrome extensions<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg01.met.vgwort.de\/na\/415a3c844b9d4e66b62d571ade40c274\" width=\"1\" height=\"1\">Google provides administrators with policies to manage the Google Chrome browser on Windows. For example, in order to manage the extensions that users are allowed to install on Chrome, there was a policy \"Configure block list for installing extensions\", which refers to the keys:<\/p>\n<p>HKEY_LOCAL_MACHINE <br \/>HKEY_CURRENT_USER<\/p>\n<p>and was managed via <em>Software\\Policies\\Google\\Chrome\\ExtensionInstallBlacklist<\/em>. However, Google has <a href=\"https:\/\/support.google.com\/chrome\/a\/answer\/7643500\" target=\"_blank\" rel=\"noopener\">deemed<\/a> this policy to be outdated, it should no longer be used.&nbsp; <\/p>\n<h2>Caught in the trap<\/h2>\n<p>The whole thing has already changed with Chrome version 86 &#8211; so should be known to administrators. But the following <a href=\"https:\/\/twitter.com\/citrixguyblog\/status\/1563058691141955584\" target=\"_blank\" rel=\"noopener\">tweet<\/a> from Julian Mooren (Senior Consultant Citrix Technology) caught my eye.<\/p>\n<p><a href=\"https:\/\/twitter.com\/citrixguyblog\/status\/1563058691141955584\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" title=\"Chrome ADMX changes\" alt=\"Chrome ADMX changes\" src=\"https:\/\/i.imgur.com\/EXxeQqG.png\"><\/a>&nbsp;<\/p>\n<p>Mooren was surprised that Google Chrome users could suddenly install all Chrome extensions from the store in Virtual Desktops. He had defined a nice blacklist via group policy. When he looked it up, he found out that Google had renamed the policy with build 86 of the Chrome browser. Instead of <em>ExtensionInstall<strong>Black<\/strong>list<\/em> the key is now called <em>ExtensionInstall<strong>Block<\/strong>list<\/em>. <\/p>\n<p>Only one letter in the name has changed &#8211; easy to overlook. As a result, extensions are no longer blocked. Those who use the updated ADMX files for Chrome can use the new blacklist policy. But probably all this is known for a long time. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]Small information\/reminder for administrators who use Google Chrome in corporate environments on Windows and manage the installation of Chrome Extensions by users via group policies. As of Chrome 86, the naming of a policy has changed &#8211; those who have &hellip; <a href=\"https:\/\/borncity.com\/win\/2022\/08\/29\/google-chrome-blockliste-fr-erweiterungen-admx-in-build-86-gendert\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[872,580,2],"tags":[780,69,194],"class_list":["post-26307","post","type-post","status-publish","format-standard","hentry","category-browser","category-security","category-windows","tag-chrome","tag-security","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/26307","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=26307"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/26307\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=26307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=26307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=26307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}