Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 281 - 290 of 433 for tls (0.3 seconds)

  1. docs/uk/docs/deployment/https.md

    Ця взаємодія між клієнтом і сервером для встановлення з'єднання TLS називається **TLS рукостисканням**.
    
    ### TLS із розширенням SNI { #tls-with-sni-extension }
    
    **Лише один процес** на сервері може слухати конкретний **порт** на конкретній **IP-адресі**. Інші процеси можуть слухати інші порти на тій самій IP-адресі, але лише один для кожної комбінації IP-адреси та порту.
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 19 18:27:41 GMT 2026
    - 21.6K bytes
    - Click Count (0)
  2. cmd/admin-handlers.go

    				Objects:      infoMessage.Objects,
    				Usage:        infoMessage.Usage,
    				Services:     infoMessage.Services,
    				Backend:      infoMessage.Backend,
    				Servers:      servers,
    				TLS:          &tls,
    				IsKubernetes: &isK8s,
    				IsDocker:     &isDocker,
    				Metrics:      getRealtimeMetrics(),
    			}
    			partialWrite(healthInfo)
    		}
    	}()
    }
    
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Sep 28 20:59:21 GMT 2025
    - 99.7K bytes
    - Click Count (0)
  3. CHANGELOG/CHANGELOG-1.11.md

    * `kubeadm join` is now blocking on the kubelet performing the TLS Bootstrap properly. Earlier, `kubeadm join` only did the discovery part and exited successfully without checking that the kubelet actually started properly and performed the TLS bootstrap correctly. Now, as kubeadm runs some post-join steps (for example, annotating the Node API object with the CRISocket), `kubeadm join` is now waiting for the kubelet to perform the TLS Bootstrap, and then uses that credential to perform further actions....
    Created: Fri Apr 03 09:05:14 GMT 2026
    - Last Modified: Thu Feb 06 06:04:15 GMT 2020
    - 328.4K bytes
    - Click Count (0)
  4. docs/tr/docs/deployment/https.md

    Client ile server arasındaki, TLS bağlantısını kurmaya yönelik bu etkileşime **TLS handshake** denir.
    
    ### SNI Extension’ı ile TLS { #tls-with-sni-extension }
    
    Server’da, belirli bir **IP adresindeki** belirli bir **portu** dinleyen **yalnızca bir process** olabilir. Aynı IP adresinde başka portları dinleyen başka process’ler olabilir, ancak IP+port kombinasyonu başına yalnızca bir tane olur.
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Fri Mar 20 07:53:17 GMT 2026
    - 14.8K bytes
    - Click Count (0)
  5. docs/pt/docs/deployment/https.md

    Esse interação entre o cliente e o servidor para estabelecer uma conexão TLS é chamada de Handshake TLS.
    
    ### TLS com a Extensão SNI { #tls-with-sni-extension }
    
    Apenas um processo no servidor pode se conectar a uma porta em um endereço IP. Poderiam existir outros processos conectados em outras portas desse mesmo endereço IP, mas apenas um para cada combinação de endereço IP e porta.
    
    TLS (HTTPS) usa a porta `443` por padrão. Então essa é a porta que precisamos.
    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)
  6. okhttp/src/commonJvmAndroid/kotlin/okhttp3/Cache.kt

         * each on their own line. A length of -1 is used to encode a null array. The last line is
         * optional. If present, it contains the TLS version.
         */
        @Throws(IOException::class)
        constructor(rawSource: Source) {
          rawSource.use {
            val source = rawSource.buffer()
            val urlLine = source.readUtf8LineStrict()
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Fri Mar 20 09:13:37 GMT 2026
    - 26.9K bytes
    - Click Count (0)
  7. docs/ru/docs/deployment/https.md

    ### TLS с расширением SNI { #tls-with-sni-extension }
    
    На сервере **только один процесс** может слушать конкретный **порт** на конкретном **IP‑адресе**. Могут быть другие процессы, слушающие другие порты на том же IP‑адресе, но не более одного процесса на каждую комбинацию IP‑адреса и порта.
    
    По умолчанию TLS (HTTPS) использует порт `443`. Значит, он нам и нужен.
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 19 17:56:20 GMT 2026
    - 22.7K bytes
    - Click Count (0)
  8. docs/de/docs/deployment/https.md

    <img src="/img/deployment/https/https02.drawio.svg">
    
    Diese Interaktion zwischen dem Client und dem Server zum Aufbau der TLS-Verbindung wird als **<abbr title="TLS-Handschlag">TLS-Handshake</abbr>** bezeichnet.
    
    ### TLS mit SNI-Erweiterung { #tls-with-sni-extension }
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 19 17:58:09 GMT 2026
    - 15.8K bytes
    - Click Count (0)
  9. CHANGELOG/CHANGELOG-1.8.md

            * requests for a TLS client certificate for any node are approved if the CSR creator has `create` permission on the `certificatesigningrequests` resource and `nodeclient` subresource in the `certificates.k8s.io` API group
    Created: Fri Apr 03 09:05:14 GMT 2026
    - Last Modified: Tue Feb 20 15:45:02 GMT 2024
    - 312.2K bytes
    - Click Count (0)
  10. CHANGELOG/CHANGELOG-1.10.md

        * --boot_id_file
        * --container_hints
        * --containerd
        * --docker
        * --docker_env_metadata_whitelist
        * --docker_only
        * --docker-tls
        * --docker-tls-ca
        * --docker-tls-cert
        * --docker-tls-key
        * --enable_load_reader
        * --event_storage_age_limit
        * --event_storage_event_limit
        * --global_housekeeping_interval
        * --google-json-key
    Created: Fri Apr 03 09:05:14 GMT 2026
    - Last Modified: Thu May 05 13:44:43 GMT 2022
    - 341.8K bytes
    - Click Count (0)
Back to Top