Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 10 of 293 for certifican (0.16 seconds)

  1. docs/es/docs/deployment/https.md

    En este caso, usaría el certificado para `someapp.example.com`.
    
    <img src="/img/deployment/https/https03.drawio.svg">
    
    El cliente ya **confía** en la entidad que generó ese certificado TLS (en este caso Let's Encrypt, pero lo veremos más adelante), por lo que puede **verificar** que el certificado sea válido.
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 19 18:15:55 GMT 2026
    - 15.1K bytes
    - Click Count (0)
  2. okhttp-tls/src/main/kotlin/okhttp3/tls/internal/der/Certificate.kt

        val data = CertificateAdapters.certificate.toDer(this)
        try {
          val certificateFactory = CertificateFactory.getInstance("X.509")
          val certificates = certificateFactory.generateCertificates(Buffer().write(data).inputStream())
          return certificates.single() as X509Certificate
        } catch (e: NoSuchElementException) {
          throw IllegalArgumentException("failed to decode certificate", e)
        } catch (e: IllegalArgumentException) {
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Mon Jan 08 01:13:22 GMT 2024
    - 6.4K bytes
    - Click Count (0)
  3. docs/fr/docs/deployment/https.md

    Le Proxy de terminaison TLS aurait accès à un ou plusieurs **certificats TLS** (certificats HTTPS).
    
    En utilisant l'**extension SNI** mentionnée plus haut, le Proxy de terminaison TLS vérifierait lequel des certificats TLS (HTTPS) disponibles il devrait utiliser pour cette connexion, en choisissant celui qui correspond au domaine attendu par le client.
    
    Dans ce cas, il utiliserait le certificat pour `someapp.example.com`.
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 19 18:37:13 GMT 2026
    - 15.8K bytes
    - Click Count (0)
  4. docs/pt/docs/deployment/https.md

    Nesse caso, ele usaria o certificado para `someapp.example.com`.
    
    <img src="/img/deployment/https/https03.drawio.svg">
    
    O cliente já confia na entidade que gerou o certificado TLS (nesse caso, o Let's Encrypt, mas veremos sobre isso mais tarde), então ele pode verificar que o certificado é válido.
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 19 18:20:43 GMT 2026
    - 14.6K bytes
    - Click Count (0)
  5. okhttp/src/jvmTest/kotlin/okhttp3/CertificatePinnerTest.kt

        }
    
        // Should not be pinned:
        certificatePinner.check("uk", listOf(certB1.certificate))
        certificatePinner.check("co.uk", listOf(certB1.certificate))
        certificatePinner.check("anotherexample.co.uk", listOf(certB1.certificate))
        certificatePinner.check("foo.anotherexample.co.uk", listOf(certB1.certificate))
      }
    
      @Test
      fun testBadPin() {
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Wed Mar 19 19:25:20 GMT 2025
    - 10.1K bytes
    - Click Count (0)
  6. okhttp-tls/README.md

        .heldCertificate(serverCertificate, intermediateCertificate.certificate())
        .build();
    ```
    
    The client only needs to know the trusted root certificate. It checks the server's certificate by
    validating the signatures within the chain.
    
    ```java
    HandshakeCertificates clientCertificates = new HandshakeCertificates.Builder()
        .addTrustedCertificate(rootCertificate.certificate())
        .build();
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Sun Mar 15 09:01:42 GMT 2026
    - 9.1K bytes
    - Click Count (0)
  7. docs/tls/README.md

    ```
    
    ### 3.2 Use OpenSSL to Generate a Certificate
    
    Use one of the following methods to generate a certificate using `openssl`:
    
    * 3.2.1 [Generate a private key with ECDSA](#generate-private-key-with-ecdsa)
    * 3.2.2 [Generate a private key with RSA](#generate-private-key-with-rsa)
    * 3.2.3 [Generate a self-signed certificate](#generate-a-self-signed-certificate)
    
    #### 3.2.1 Generate a private key with ECDSA
    
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 8.6K bytes
    - Click Count (0)
  8. okhttp-tls/src/main/kotlin/okhttp3/tls/HandshakeCertificates.kt

     *
     *  * The server's handshake certificates must have a [held certificate][HeldCertificate] (a
     *    certificate and its private key). The certificate's subject alternative names must match the
     *    server's hostname. The server must also have is a (possibly-empty) chain of intermediate
     *    certificates to establish trust from a root certificate to the server's certificate. The root
     *    certificate is not included in this chain.
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Sat May 10 11:15:14 GMT 2025
    - 8.4K bytes
    - Click Count (0)
  9. okhttp-tls/src/test/java/okhttp3/tls/internal/der/DerCertificatesTest.kt

        val certificate =
          HeldCertificate
            .Builder()
            .keyPair(publicKey, privateKey)
            .build()
    
        val certificateByteString = certificate.certificate.encoded.toByteString()
    
        val okHttpCertificate =
          CertificateAdapters.certificate
            .fromDer(certificateByteString)
    
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Wed Mar 19 19:25:20 GMT 2025
    - 43.9K bytes
    - Click Count (0)
  10. okhttp-tls/src/main/kotlin/okhttp3/tls/HeldCertificate.kt

     * ```
     *
     * In this example the HTTP client already knows and trusts the last certificate, "Entrust Root
     * Certification Authority - G2". That certificate is used to verify the signature of the
     * intermediate certificate, "Entrust Certification Authority - L1M". The intermediate certificate
     * is used to verify the signature of the "www.squareup.com" certificate.
     *
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Tue Jan 27 09:00:39 GMT 2026
    - 21.6K bytes
    - Click Count (0)
Back to Top