- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 187 for tls (3.48 sec)
-
cni/pkg/install/testdata/kubeconfig-tls
John Howard <******@****.***> 1684290142 -0700
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed May 17 02:22:22 GMT 2023 - 1.7K bytes - Viewed (0) -
cni/pkg/install/testdata/kubeconfig-skip-tls
apiVersion: v1 clusters: - cluster: insecure-skip-tls-verify: true server: https://10.96.0.1:443 name: local contexts: - context: cluster: local user: istio-cni name: istio-cni-context current-context: istio-cni-context kind: Config preferences: {} users: - name: istio-cni user:
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed May 17 02:22:22 GMT 2023 - 342 bytes - Viewed (0) -
samples/tlssurvey/src/main/resources/okhttp_3.9.txt
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Tue Apr 02 01:44:15 GMT 2024 - 542 bytes - Viewed (0) -
okhttp/src/test/java/okhttp3/ConnectionSpecTest.kt
assertThat(sslSocket.enabledCipherSuites) .containsExactly( CipherSuite.TLS_AES_128_GCM_SHA256.javaName, CipherSuite.TLS_AES_256_GCM_SHA384.javaName, CipherSuite.TLS_CHACHA20_POLY1305_SHA256.javaName, CipherSuite.TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256.javaName, CipherSuite.TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA.javaName, ) } else {
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 14.7K bytes - Viewed (0) -
docs/ru/docs/deployment/https.md
Прокси-сервер завершения работы TLS будет иметь доступ к одному или нескольким **TLS-сертификатам** (сертификаты HTTPS). Используя **расширение SNI** упомянутое выше, прокси-сервер из имеющихся сертификатов TLS (HTTPS) выберет тот, который соответствует имени домена, указанному в запросе от клиента. То есть будет выбран сертификат для домена `someapp.example.com`.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Apr 03 16:22:47 GMT 2024 - 20.6K bytes - Viewed (0) -
okhttp/src/test/java/okhttp3/CipherSuiteTest.kt
socket.enabledProtocols = arrayOf("TLSv1") socket.supportedCipherSuites = arrayOf("TLS_A", "TLS_B", "TLS_C", "TLS_D", "TLS_E") socket.enabledCipherSuites = arrayOf("TLS_A", "TLS_B", "TLS_C") val connectionSpec = ConnectionSpec.Builder(true) .tlsVersions(TlsVersion.TLS_1_0) .cipherSuites("SSL_A", "SSL_C", "SSL_E") .build() applyConnectionSpec(connectionSpec, socket, false)
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 8.2K bytes - Viewed (0) -
samples/tlssurvey/src/main/resources/okhttp_3.14.txt
TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Tue Apr 02 01:44:15 GMT 2024 - 543 bytes - Viewed (0) -
okhttp-tls/src/main/kotlin/okhttp3/tls/HandshakeCertificates.kt
import okhttp3.tls.internal.TlsUtil.newKeyManager import okhttp3.tls.internal.TlsUtil.newTrustManager /** * Certificates to identify which peers to trust and also to earn the trust of those peers in kind. * Client and server exchange these certificates during the handshake phase of a TLS connection. * * ### Server Authentication *
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
As only one process can be listening on this port, the process that would do it would be the **TLS Termination Proxy**. The TLS Termination Proxy would have access to one or more **TLS certificates** (HTTPS certificates). Using the **SNI extension** discussed above, the TLS Termination Proxy would check which of the TLS (HTTPS) certificates available it should use for this connection, using the one that matches the domain expected by the client.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 12K bytes - Viewed (0) -
okhttp/src/test/java/okhttp3/internal/connection/RetryConnectionTest.kt
ConnectionSpec.Builder(ConnectionSpec.MODERN_TLS) .tlsVersions(TlsVersion.SSL_3_0) .build() val routePlanner = factory.newRoutePlanner(client) val route = factory.newRoute() val connectionSpecs = listOf(ConnectionSpec.MODERN_TLS, ConnectionSpec.COMPATIBLE_TLS, sslV3) val enabledSocketTlsVersions = arrayOf( TlsVersion.TLS_1_2, TlsVersion.TLS_1_1, TlsVersion.TLS_1_0, )
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 4.3K bytes - Viewed (0)