Hi Hubert and Matt,
I hope this email finds you well! We noticed some new certificate-related policies in Chromium in this folder: CertificateManagement - Chromium Code Search, but since they're marked as "future" policies, we're not sure what the envisioned use case is for them.We are hoping you can share some context on the intended use cases for these policies. Do you have some specific enterprise scenarios requesting controls like this?
Best,Celeste
--
You received this message because you are subscribed to the Google Groups "chrome-secure-web-and-net" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-secure-web-...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chrome-secure-web-and-net/CAGTM%2B7gLHvWt%3Dzup3eEZ1RTOm1wL-N7zYJGJ18RZ4sZkuV2iGw%40mail.gmail.com.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.
Hi,
I agree the descriptions are sufficient to understand what they do.
The question was more about motivation—the goal is to enable further decoupling from the OS root store, correct? We were hoping to understand if there was anything more nuanced than, “give me consistent cross-platform policies for managing Chrome.” For example, I could imagine maybe you’ve had customers request the ability to install a root to the OS store but they want to do so in a way that doesn’t affect the browser.
Given we’re not actively getting similar requests (at least, not that I’m aware of), we wanted to check if we were missing anything.
If the answer is, “we’ve have requests but are not willing to share more than that,” that’s fine too. Thanks for the quick response either way!
Thanks,
Erik