- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 246 for certifikat (0.23 sec)
-
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) {
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 6.4K bytes - Viewed (0) -
docs/de/docs/deployment/https.md
Der TLS-Terminierungsproxy hätte Zugriff auf ein oder mehrere **TLS-Zertifikate** (HTTPS-Zertifikate). Mithilfe der oben beschriebenen **SNI-Erweiterung** würde der TLS-Terminierungsproxy herausfinden, welches der verfügbaren TLS-Zertifikate (HTTPS) er für diese Verbindung verwenden muss, und zwar das, welches mit der vom Client erwarteten Domain übereinstimmt. In diesem Fall würde er das Zertifikat für `someapp.example.com` verwenden.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Sat Mar 30 20:16:46 GMT 2024 - 13.5K bytes - Viewed (0) -
docs/fr/docs/deployment/https.md
* C'est une couche en dessous de HTTP. * Donc, le certificat et le traitement du cryptage sont faits avant HTTP. * TCP ne connaît pas les "domaines", seulement les adresses IP. * L'information sur le domaine spécifique demandé se trouve dans les données HTTP. * Les certificats HTTPS "certifient" un certain domaine, mais le protocole et le cryptage se font au niveau TCP, avant de savoir quel domaine est traité.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Mon Oct 31 17:45:30 GMT 2022 - 4.1K bytes - Viewed (0) -
docs/de/docs/deployment/concepts.md
* HAProxy * Mit einer externen Komponente wie Certbot für Zertifikat-Erneuerungen * Kubernetes mit einem Ingress Controller wie Nginx * Mit einer externen Komponente wie cert-manager für Zertifikat-Erneuerungen * Es wird intern von einem Cloud-Anbieter als Teil seiner Dienste verwaltet (siehe unten 👇)
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Sat Mar 30 20:16:25 GMT 2024 - 20.6K bytes - Viewed (0) -
okhttp-tls/src/test/java/okhttp3/tls/HeldCertificateTest.kt
val certificate = heldCertificate.certificate assertThat(certificate.getSubjectX500Principal().name, "self-signed") .isEqualTo(certificate.getIssuerX500Principal().name) assertThat(certificate.getIssuerX500Principal().name).matches(Regex("CN=[0-9a-f-]{36}")) assertThat(certificate.serialNumber).isEqualTo(BigInteger.ONE) assertThat(certificate.subjectAlternativeNames).isNull()
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 22.5K bytes - Viewed (0) -
okhttp-tls/src/main/kotlin/okhttp3/tls/Certificates.kt
throw IllegalArgumentException("failed to decode certificate", nsee) } catch (iae: IllegalArgumentException) { throw IllegalArgumentException("failed to decode certificate", iae) } catch (e: GeneralSecurityException) { throw IllegalArgumentException("failed to decode certificate", e) } } /** * Returns the certificate encoded in [PEM format][rfc_7468]. *
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 2.8K bytes - Viewed (2) -
docs/features/https.md
on-300-000-iranians-using-fake-google-certificate.html). It also assumes your HTTPS servers’ certificates are signed by a certificate authority. Use [CertificatePinner](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-certificate-pinner/) to restrict which certificates and certificate authorities are trusted. Certificate pinning increases security, but limits your server team’s abilities to update their TLS certificates. **Do not use certificate pinning without the blessing of your server’s...
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sat Dec 24 00:16:30 GMT 2022 - 10.5K bytes - Viewed (0) -
okhttp/src/test/java/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() {
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 9.9K bytes - Viewed (0) -
samples/guide/src/main/java/okhttp3/recipes/CheckHandshake.java
@Override public Response intercept(Chain chain) throws IOException { for (Certificate certificate : chain.connection().handshake().peerCertificates()) { String pin = CertificatePinner.pin(certificate); if (denylist.contains(pin)) { throw new IOException("Denylisted peer certificate: " + pin); } } return chain.proceed(chain.request()); } };
Java - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Apr 15 14:55:09 GMT 2024 - 2.1K bytes - Viewed (0) -
okhttp/src/test/java/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.Builder()
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 23.8K bytes - Viewed (0)