Lines Matching full:trusted
60 server is not to be trusted.</p>
165 because you have a CA that isn't trusted by the system. It could be because
166 you have a certificate from a new CA that isn't yet trusted by Android or your app is
179 will be the only CAs trusted by that {@link javax.net.ssl.TrustManager}.</p>
205 // Create a KeyStore containing our trusted CAs
231 that your server certificate come from a trusted issuer.</p>
241 validates that the certificate comes from a trusted
277 trusted root CA.</p>
298 trusted by Android.</p>
315 cause. This is because most desktop browsers cache trusted intermediate CAs over time. Once
341 is to verify the certificate is from a trusted source, which was the focus of the previous
498 above to restrict an app's trusted CAs to a small set known to be used by the app's servers. This
