Bug#956012: Frightening!
I agree that it's a pretty annoying and scary message (and incorrect - "If a software program on your system has set enterprise policies that affect how Chrome works, you’ll see this message—even if it’s not fully managed by an organization." https://www.howtogeek.com/410106/why-does-chrome-say-its-managed-by-your-organization/ ). I'll switch it to using master_preferences so that message goes away, although it also means that some people who were switched to DDG will be switched back to Google. On Sun, Aug 21, 2022 at 22:12, Steve McIntyre wrote: Nod. Even as an experienced user and developer, I was very surprised to see this message. I have quite a few account identities set up in my Chromium (e.g. for Google services), but I would never expect any of them to be described as managing it. -- Steve McIntyre, Cambridge, UK. st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Bug#956012: Frightening!
arthurweinber...@gmail.com wrote: > >Hi Mike, > >"Frightening" is my perspective on this. > >When an average user sees their chromium is suddenly "managed" by their >organization and they know they are not part of any organization, then >their first idea will be that they have been hacked. In my case I deleted >my entire chromium profile before I realized that this was the root cause. > >I hope you quickly rollback this change to save others this pain and then >figure out a better way to roll this forward. Nod. Even as an experienced user and developer, I was very surprised to see this message. I have quite a few account identities set up in my Chromium (e.g. for Google services), but I would never expect any of them to be described as managing it. -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Bug#956012: Frightening!
Hi Mike,
"Frightening" is my perspective on this.
When an average user sees their chromium is suddenly "managed" by their
organization and they know they are not part of any organization, then
their first idea will be that they have been hacked. In my case I deleted
my entire chromium profile before I realized that this was the root cause.
I hope you quickly rollback this change to save others this pain and then
figure out a better way to roll this forward.
Thanks
Arthur Weinberger
arthurweinber...@gmail.com
On Sun, Aug 21, 2022 at 9:13 AM Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:
> Hi Andres,
>
> On So 21 Aug 2022 09:47:51 CEST, Andres Salomon wrote:
>
> > 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}=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. 樂
>
> why is this frightening? (your mail subject). Many distributors tinker
> with that master_preferences file for their likings.
>
> And policies/managed is definitely the wrong place for configuring the
> search provider, as that means that users can't change it.
>
> Another option is putting the default search provider in
> policies/recommended. Haven't tested it, but it should work, as well.
>
> See https://sunweavers.net/blog/node/135 for details / overview of
> tweaking features.
>
> Mike
>
>
> --
>
> DAS-NETZWERKTEAM
> c\o Technik- und Ökologiezentrum Eckernförde
> Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
> mobile: +49 (1520) 1976 148
> landline: +49 (4351) 850 8940
>
> GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
> mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
>
>
Bug#956012: Frightening!
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}=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
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
Bug#956012: Frightening!
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
