4 ms·
Reporting that there is a policy is no bug, but maybe there should be a way to signify that it's customized by your software vendor (i.e. signed and keys are co
by sascha_sl 4y ago
Reporting that there is a policy is no bug, but maybe there should be a way to signify that it's customized by your software vendor (i.e. signed and keys are compiled in) and that it just sets the default search engine.
Chromium does change the message to "This device is managed by <google workspaces domain>" if attached to Chrome Enterprise.
- brnt 4y agoBeing "managed by" and loading a policy config do not equate in meaning, unless we let PR departments redefine words. Moreover, defaulting to Google is also a policy.
- sascha_sl 4y agoThe intent behind policy loading in Chrome is to allow an MDM to configure the browser, not for distros to not write a real patch.
- brnt 4y agoPerhaps. Describing loading a custom policy with "managed by" is still incorrect and potentially misleading.
- kccqzy 4y agoThe policy config is designed for enterprises, not software distributors. It's Debian that's taking an unnecessary shortcut here. They could've patched the source code to change the default search engine.