It looks like the other way to do this is through
/etc/chromium/master_preferences, which will only take effect when
people first install and run chromium.
"search_provider_overrides": [{
"enabled": true,
"encoding": "UTF-8",
"favicon_url": "https://duckduckgo.com/favicon.ico",
"new_tab_url": "https://duckduckgo.com/chrome_newtab",
"id": 2,
"keyword": "duckduckgo.com",
"name": "DuckDuckGo",
"search_url": "https://duckduckgo.com/?q={searchTerms}",
"suggest_url":
"https://duckduckgo.com/ac/?q={searchTerms}&type=list"
}],
"search_provider_overrides_version": 1,
It's not clear if that's the route we should go, but it does get rid of
the notices about the browser being managed by an organization. 🤔
On Sat, Aug 20, 2022 at 22:56, Arthur Weinberger
<arthurweinber...@gmail.com> wrote:
Hi,
This change caused my chromium browser to report that it's being
managed by my "organization". I thought that my machine was somehow
compromised. This is terrifying! I wound up deleting my entire
chromium profile before I discovered that the root cause was this
DuckDuckGo config change. Even in the "recommended" subdirectory,
chromium still reports that it's being managed. This is terrifying! I
hope you revert this change to save others from the panic I went
through.
The patch approach listed in this thread might be a better way.
Thanks
Arthur Weinberger