- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 42 for Trusted (0.46 sec)
-
okhttp/src/main/kotlin/okhttp3/internal/tls/BasicCertificateChainCleaner.kt
val toVerify = result[result.size - 1] as X509Certificate // If this cert has been signed by a trusted cert, use that. Add the trusted certificate to // the end of the chain unless it's already present. (That would happen if the first // certificate in the chain is itself a self-signed and trusted CA certificate.) val trustedCert = trustRootIndex.findByIssuerAndSignature(toVerify) if (trustedCert != null) {
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 4.8K bytes - Viewed (0) -
okhttp-tls/src/main/kotlin/okhttp3/tls/HandshakeCertificates.kt
/** * Configure the certificate chain to use when being authenticated. The first certificate is * the held certificate, further certificates are included in the handshake so the peer can * build a trusted path to a trusted root certificate. * * The chain should include all intermediate certificates but does not need the root certificate * that we expect to be known by the remote peer. The peer already has that certificate so
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 8.5K bytes - Viewed (1) -
docs/en/docs/deployment/https.md
* Traefik (that can also handle certificate renewals) * Caddy (that can also handle certificate renewals) * Nginx * HAProxy ## Let's Encrypt Before Let's Encrypt, these **HTTPS certificates** were sold by trusted third parties. The process to acquire one of these certificates used to be cumbersome, require quite some paperwork and the certificates were quite expensive.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 12K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/tls/CertificateChainCleaner.kt
* certificate is signed by the certificate that follows, and the last certificate is a trusted CA * certificate. * * Use of the chain cleaner is necessary to omit unexpected certificates that aren't relevant to * the TLS handshake and to extract the trusted CA certificate for the benefit of certificate * pinning. */ abstract class CertificateChainCleaner {
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 2K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/platform/AndroidPlatform.kt
* * This class exploits knowledge of Android implementation details. This class is potentially * much faster to initialize than [BasicTrustRootIndex] because it doesn't need to load and * index trusted CA certificates. */ internal data class CustomTrustRootIndex( private val trustManager: X509TrustManager, private val findByIssuerAndSignatureMethod: Method, ) : TrustRootIndex {
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 6.2K bytes - Viewed (0) -
okhttp-tls/src/main/kotlin/okhttp3/tls/HeldCertificate.kt
* called certificate authorities (CAs). * * Browsers and other HTTP clients need a set of trusted root certificates to authenticate their * peers. Sets of root certificates are managed by either the HTTP client (like Firefox), or the * host platform (like Android). In July 2018 Android had 134 trusted root certificates for its HTTP * clients to trust. *
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 21.6K bytes - Viewed (1) -
docs/en/docs/alternatives.md
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 23.2K bytes - Viewed (0) -
docs/changelogs/changelog_4x.md
* Fix: Handshake now returns peer certificates in canonical order: each certificate is signed by the certificate that follows and the last certificate is signed by a trusted root. * Fix: Don't lose HTTP/2 flow control bytes when incoming data races with a stream close. If this happened enough then eventually the connection would stall.
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Wed Apr 17 13:25:31 GMT 2024 - 25.2K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/CertificatePinner.kt
import okhttp3.internal.toCanonicalHost import okio.ByteString import okio.ByteString.Companion.decodeBase64 import okio.ByteString.Companion.toByteString /** * Constrains which certificates are trusted. Pinning certificates defends against attacks on * certificate authorities. It also prevents connections through man-in-the-middle certificate * authorities either known or unknown to the application's user.
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 14.2K bytes - Viewed (1) -
docs/security/README.md
#### Figure 2 - KMS key hierarchy ``` CMK (master key)
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 13.8K bytes - Viewed (0)