Comment #2 on issue 7147 by adamsc: Mac Chrome should be able to be centrally managed with MCX preferences/manifest http://code.google.com/p/chromium/issues/detail?id=7147
Two comments: * If Chrome does not use the Keychain (i.e. using CA certificates from /Library/Keychains/System.keychain) it would be extremely important to have some option to manage Chrome's CA store and trust settings (e.g. whether OCSP is required). This is one of the biggest drawbacks to Firefox deployment on all platforms at large institutions. * Since Chrome is nowhere near as widely deployed as Safari but should be, it'd be handy if Chrome supported Safari's preferences (See com.apple.Safari.manifest) where applicable unless overridden so e.g. proxy, security or homepage settings "just work" if Chrome is launched on a system where Safari is managed. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
