Hacker News new | past | comments | ask | show | jobs | submit login

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.




Being "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.


The 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.


The intent behind policy loading in Chrome is to allow an MDM to configure the browser, not for distros to not write a real patch.


Perhaps. Describing loading a custom policy with "managed by" is still incorrect and potentially misleading.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: