- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 127 for certificado (0.09 sec)
-
docs/pt/docs/deployment/https.md
* Traefik (que também pode gerenciar a renovação de certificados) * Caddy (que também pode gerenciar a renovação de certificados) * Nginx * HAProxy ## Let's Encrypt Antes de Let's Encrypt, esses **certificados HTTPS** eram vendidos por terceiros confiáveis. O processo de aquisição de um desses certificados costumava ser complicado, exigia bastante papelada e os certificados eram bastante caros.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 12.8K bytes - Viewed (0) -
docs/es/docs/deployment/https.md
* Traefik (que también puede manejar la renovación de certificados) * Caddy (que también puede manejar la renovación de certificados) * Nginx * HAProxy ## Let's Encrypt Antes de Let's Encrypt, estos **certificados HTTPS** eran vendidos por terceros. El proceso para adquirir uno de estos certificados solía ser complicado, requerir bastante papeleo y los certificados eran bastante costosos.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 13K bytes - Viewed (0) -
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) {
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Mon Jan 08 01:13:22 UTC 2024 - 6.4K bytes - Viewed (0) -
docs/fr/docs/deployment/https.md
Maintenant, du point de vue d'un développeur, voici plusieurs choses à avoir en tête en pensant au HTTPS : * Pour le HTTPS, le serveur a besoin de "certificats" générés par une tierce partie. * Ces certificats sont en fait acquis auprès de la tierce partie, et non "générés". * Les certificats ont une durée de vie. * Ils expirent. * Puis ils doivent être renouvelés et acquis à nouveau auprès de la tierce partie.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 4.1K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/internal/tls/CertificatePinnerChainValidationTest.kt
// Add a bad intermediate CA and have that issue a rogue certificate for localhost. Prepare // an SSL context for an attacking webserver. It includes both these rogue certificates plus the // trusted good certificate above. The attack is that by including the good certificate in the // chain, we may trick the certificate pinner into accepting the rouge certificate. val compromisedIntermediateCa = HeldCertificate
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Fri Jun 20 11:46:46 UTC 2025 - 24.3K bytes - Viewed (1) -
okhttp/src/jvmTest/kotlin/okhttp3/HandshakeTest.kt
peerCertificates = listOf(serverCertificate.certificate, serverIntermediate.certificate), localCertificates = listOf(), ) assertThat(handshake.tlsVersion).isEqualTo(TlsVersion.TLS_1_3) assertThat(handshake.cipherSuite).isEqualTo(CipherSuite.TLS_AES_128_GCM_SHA256) assertThat(handshake.peerCertificates).containsExactly( serverCertificate.certificate, serverIntermediate.certificate, )
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 4.2K bytes - Viewed (0) -
docs/pt/docs/deployment/concepts.md
E tem que haver algo responsável por **renovar os certificados HTTPS**, pode ser o mesmo componente ou pode ser algo diferente. ### Ferramentas de exemplo para HTTPS Algumas das ferramentas que você pode usar como um proxy de terminação TLS são: * Traefik * Lida automaticamente com renovações de certificados ✨ * Caddy * Lida automaticamente com renovações de certificados ✨ * Nginx
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 19.7K bytes - Viewed (0) -
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. *
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 21.6K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/CertificateChainCleanerTest.kt
.serialNumber(1L) .build() val rootB = HeldCertificate .Builder() .serialNumber(2L) .build() assertThat(get(rootB.certificate, rootA.certificate)) .isEqualTo(get(rootA.certificate, rootB.certificate)) } @Test fun equalsFromTrustManager() { val handshakeCertificates = HandshakeCertificates.Builder().build()
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 9.5K bytes - Viewed (1) -
okhttp/src/commonJvmAndroid/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 { @Throws(SSLPeerUnverifiedException::class)
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 2K bytes - Viewed (0)