Lines Matching full:these

68 These policies only apply to publicly-trusted CAs - that is, CAs that your
94 the site supports CT, then these certificates will be rejected as untrusted, and
116 these datasets, in many cases, the certificate details and domains were already
155    certificate, but these certificates will **only** be trusted by their
195 trusting this CA. In these cases, the Enterprise can use
203 enable these domains to be kept private, while allowing the certificates to
207 to serve these domains, as they are organization specific. For example, such
217 [Enterprise Policies](#Enterprise-Policies) to enable these certificates to be
231 requirements. These CAs would not be trusted in new products, nor other root
240 Organizations that need to use certificates from these CAs should be aware
243 may be the only way to ensure these certificates continue to work, but that
247 Organizations that need to trust certificates from these CAs, such as when
248 talking to other organizations that need to use these CAs, can configure
250 which will allow trust in these certificates. As these only apply to Enterprise
251 users, these policies are not suitable for making these certificates trusted
258 These policies are documented in the
296 To disable Certificate Transparency for these certificates, the certificate
321 However, these CAs must also be recognized as Legacy CAs in the
348 In addition to these two core classes, configuration and support for CT-related
383 held to gather key stakeholders together to work through these issues, helping