/Zephyr-latest/include/zephyr/net/ |
D | tls_credentials.h | 8 * @brief TLS credentials management 10 * An API for applications to configure TLS credentials. 17 * @brief TLS credentials management 18 * @defgroup tls_credentials TLS credentials management 29 /** TLS credential types */ 61 /** Secure tag, a reference to TLS credential 66 * @note Some TLS credentials come in pairs: 77 * @brief Add a TLS credential. 79 * @details This function adds a TLS credential, that can be used 80 * by TLS/DTLS for authentication. [all …]
|
/Zephyr-latest/subsys/net/lib/tls_credentials/ |
D | Kconfig | 5 bool "TLS credentials management" 7 Enable TLS credentials management subsystem. 16 prompt "TLS credentials management backend" 20 TLS credentials management backend implementation. 23 bool "TLS credentials management volatile backend" 25 TLS credentials management volatile backend implementation, 29 bool "TLS credentials management protected storage backend" 33 TLS credentials management backend using the Protected Storage 40 int "Maximum number of TLS credentials" 43 Maximum number of TLS credentials that can be registered. [all …]
|
D | tls_internal.h | 8 * @brief Internal API for fetching TLS credentials 16 /* Internal structure representing TLS credential. */ 18 /* TLS credential type. */ 36 /* Lock TLS credential access. */ 39 /* Unlock TLS credential access. */
|
/Zephyr-latest/modules/mbedtls/ |
D | Kconfig | 1 # Cryptography primitive options for mbed TLS 13 mbed TLS menu prompt and instead handle the selection of MBEDTLS from 20 bool "mbed TLS Support" if !MBEDTLS_PROMPTLESS 46 bool "Custom mbed TLS configuration file" 53 string "mbed TLS configuration file" if CUSTOM_MBEDTLS_CFG_FILE 55 default "config-tls-generic.h" 61 special TLS usage, use available Kconfig options, or select an 64 rsource "Kconfig.tls-generic" 67 int "Max payload size for TLS protocol message" 71 The TLS standards mandate max payload size of 16384 bytes. So, for [all …]
|
D | Kconfig.tls-generic | 1 # TLS/DTLS related options 7 menu "Mbed TLS configuration" 8 depends on MBEDTLS_BUILTIN && MBEDTLS_CFG_FILE = "config-tls-generic.h" 10 menu "TLS" menu 13 bool "Support for TLS 1.2 (DTLS 1.2)" 25 bool "Support for TLS 1.3" 30 bool "Support for RFC 5077 session tickets in TLS 1.3" 41 endmenu # TLS 75 int "Max size of TLS pre-shared keys" 78 Max size of TLS pre-shared keys, in bytes. It has no effect if no [all …]
|
/Zephyr-latest/arch/arc/core/ |
D | tls.c | 25 new_thread->tls = POINTER_TO_UINT(stack_ptr); in arch_tls_stack_setup() 32 return (void *)(arch_current_thread()->tls); in _mwget_tls() 39 * TLS area for ARC has some data fields following by in arch_tls_stack_setup() 41 * used by toolchain and OS TLS code to aid in locating in arch_tls_stack_setup() 42 * the TLS data/bss. Zephyr currently has no use for in arch_tls_stack_setup() 45 * we simply skip them when setting the TLS pointer. in arch_tls_stack_setup() 50 * setup the TLS data/bss area first. in arch_tls_stack_setup() 59 * Set thread TLS pointer which is used in in arch_tls_stack_setup() 60 * context switch to point to TLS area. in arch_tls_stack_setup() 62 new_thread->tls = POINTER_TO_UINT(stack_ptr); in arch_tls_stack_setup()
|
/Zephyr-latest/arch/arm/core/ |
D | tls.c | 17 * register needed to store TLS pointer at runtime for 27 * TLS area for ARM has some data fields following by 29 * used by toolchain and OS TLS code to aid in locating 30 * the TLS data/bss. Zephyr currently has no use for 33 * we simply skip them when setting the TLS pointer. 38 * setup the TLS data/bss area first. 47 * Set thread TLS pointer which is used in 48 * context switch to point to TLS area. 50 new_thread->tls = POINTER_TO_UINT(stack_ptr);
|
/Zephyr-latest/samples/net/mqtt_publisher/ |
D | docker-test.sh | 27 # test TLS 28 echo "Starting MQTT TLS test" 31 "/usr/local/sbin/mosquitto -v -c /usr/local/etc/mosquitto/mosquitto-tls.conf" || return $? 33 start_zephyr -DOVERLAY_CONFIG="overlay-tls.conf overlay-sample.conf" "$overlay" 47 # TLS and SOCKS5, mosquitto TLS is already running 48 echo "Starting MQTT TLS + proxy test" 52 start_zephyr -DOVERLAY_CONFIG="overlay-tls.conf overlay-sample.conf overlay-socks5.conf" "$overlay"…
|
/Zephyr-latest/arch/arm64/core/ |
D | tls.c | 17 * TLS area for ARM has some data fields following by in arch_tls_stack_setup() 19 * used by toolchain and OS TLS code to aid in locating in arch_tls_stack_setup() 20 * the TLS data/bss. Zephyr currently has no use for in arch_tls_stack_setup() 23 * we simply skip them when setting the TLS pointer. in arch_tls_stack_setup() 28 * setup the TLS data/bss area first. in arch_tls_stack_setup() 37 * Set thread TLS pointer which is used in in arch_tls_stack_setup() 38 * context switch to point to TLS area. in arch_tls_stack_setup() 40 new_thread->tls = POINTER_TO_UINT(stack_ptr); in arch_tls_stack_setup()
|
/Zephyr-latest/arch/xtensa/core/ |
D | tls.c | 21 * TLS area has some data fields following by in arch_tls_stack_setup() 23 * used by toolchain and OS TLS code to aid in locating in arch_tls_stack_setup() 24 * the TLS data/bss. Zephyr currently has no use for in arch_tls_stack_setup() 27 * we simply skip them when setting the TLS pointer. in arch_tls_stack_setup() 32 * setup the TLS data/bss area first. in arch_tls_stack_setup() 41 * Set thread TLS pointer which is used in in arch_tls_stack_setup() 42 * context switch to point to TLS area. in arch_tls_stack_setup() 44 new_thread->tls = POINTER_TO_UINT(stack_ptr); in arch_tls_stack_setup()
|
/Zephyr-latest/subsys/net/lib/mqtt/ |
D | mqtt_transport_socket_tls.c | 9 * @brief Internal functions to handle transport over TLS socket. 24 struct mqtt_sec_config *tls_config = &client->transport.tls.config; in mqtt_client_tls_connect() 27 client->transport.tls.sock = zsock_socket(broker->sa_family, in mqtt_client_tls_connect() 29 if (client->transport.tls.sock < 0) { in mqtt_client_tls_connect() 33 NET_DBG("Created socket %d", client->transport.tls.sock); in mqtt_client_tls_connect() 37 ret = setsockopt(client->transport.tls.sock, in mqtt_client_tls_connect() 47 ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS, TLS_PEER_VERIFY, in mqtt_client_tls_connect() 55 ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS, in mqtt_client_tls_connect() 64 ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS, in mqtt_client_tls_connect() 75 ret = zsock_setsockopt(client->transport.tls.sock, SOL_TLS, in mqtt_client_tls_connect() [all …]
|
/Zephyr-latest/kernel/include/ |
D | kernel_tls.h | 20 * @brief Return the total size of TLS data/bss areas 22 * This returns the total size of thread local storage (TLS) 25 * bits required for proper functionality of TLS. 27 * @return Total size of TLS data/bss areas 36 * @brief Copy the TLS data/bss areas into destination 38 * This copies the TLS data into destination and clear the area 39 * of TLS bss size after the data section.
|
/Zephyr-latest/samples/net/sockets/http_get/ |
D | README.rst | 44 Enabling TLS support 47 Enable TLS support in the sample by building the project with the 48 ``overlay-tls.conf`` overlay file enabled, for example, using these commands: 53 :conf: "prj.conf overlay-tls.conf" 57 An alternative way is to specify ``-DEXTRA_CONF_FILE=overlay-tls.conf`` when 60 For boards that support TLS offloading (e.g. TI's cc3220sf_launchxl), use 61 ``overlay-tls-offload.conf`` instead of ``overlay-tls.conf``. 66 over TLS, provide an appropriate certificate to authenticate to that web server. 68 Note, that TLS support in the sample depends on non-posix, TLS socket 69 functionality. Therefore, it is only possible to run TLS in this sample
|
/Zephyr-latest/subsys/net/lib/sockets/ |
D | Kconfig | 115 bool "TCP TLS socket option support" 124 Enable TLS socket option support which automatically establishes 125 a TLS connection to the remote host. 128 int "Default processing priority for TLS sockets" 131 Processing priority for TLS sockets. Should be lower than 138 Call mbedtls_ssl_conf_max_frag_len() on created TLS context 143 MBEDTLS_SSL_OUT_CONTENT_LEN and MBEDTLS_SSL_IN_CONTENT_LEN mbed TLS 145 case of default mbed TLS config). With DTLS, MFL value may be further 148 This is mostly useful for TLS client side to tell TLS server what is 156 Enable DTLS socket support. By default only TLS over TCP is supported. [all …]
|
/Zephyr-latest/arch/riscv/core/ |
D | tls.c | 17 * TLS area for RISC-V is simple without any extra in arch_tls_stack_setup() 23 * setup the TLS data/bss area first. in arch_tls_stack_setup() 29 * Set thread TLS pointer which is used in in arch_tls_stack_setup() 30 * context switch to point to TLS area. in arch_tls_stack_setup() 32 new_thread->tls = POINTER_TO_UINT(stack_ptr); in arch_tls_stack_setup()
|
/Zephyr-latest/tests/net/socket/tls/ |
D | testcase.yaml | 8 - tls 14 net.socket.tls: 17 net.socket.tls.preempt: 21 net.socket.tls.sendmsg_no_buf:
|
/Zephyr-latest/arch/x86/core/ |
D | tls.c | 16 * TLS area for x86 and x86_64 has the data/bss first, in arch_tls_stack_setup() 28 * the pointer to the TLS area at top of stack. in arch_tls_stack_setup() 35 * Set thread TLS pointer as this is used to populate in arch_tls_stack_setup() 38 new_thread->tls = POINTER_TO_UINT(self_ptr); in arch_tls_stack_setup() 40 /* Setup the TLS data */ in arch_tls_stack_setup()
|
/Zephyr-latest/samples/net/sockets/big_http_download/ |
D | README.rst | 65 Enabling TLS support 68 Enable TLS support in the sample by building the project with the 69 ``overlay-tls.conf`` overlay file enabled, for example, using these commands: 74 :conf: "prj.conf overlay-tls.conf" 78 An alternative way is to specify ``-DEXTRA_CONF_FILE=overlay-tls.conf`` when 81 The TLS version of this sample downloads a file from 85 for TLS communication (https://launchpad.net) and possible redirects. To access 86 a different web page over TLS, you'll need to provide a different certificate 89 Note, that TLS support in the sample depends on non-posix, TLS socket 90 functionality. Therefore, it is only possible to run TLS in this sample
|
/Zephyr-latest/arch/x86/core/ia32/ |
D | tls.c | 17 * the TLS storage area in stack. Here we update one in z_x86_tls_update_gdt() 27 sd->base_low = thread->tls & 0xFFFFU; in z_x86_tls_update_gdt() 28 sd->base_mid = (thread->tls >> 16) & 0xFFU; in z_x86_tls_update_gdt() 29 sd->base_hi = (thread->tls >> 24) & 0xFFU; in z_x86_tls_update_gdt() 41 * the pointer to the TLS area at top of stack. in z_x86_early_tls_update_gdt()
|
/Zephyr-latest/modules/mbedtls/configs/ |
D | config-threadnet.h | 2 * Minimal configuration for using TLS as part of Thread 19 * This file is part of mbed TLS (https://tls.mbed.org) 23 * Minimal configuration for using TLS a part of Thread 59 /* mbed TLS feature support */ 71 /* mbed TLS modules */
|
/Zephyr-latest/samples/net/sockets/http_client/ |
D | docker-test.sh | 10 # First the non-tls version 25 # If everything is ok so far, do the TLS version 29 overlay="${zephyr_overlay};overlay-tls.conf" 31 overlay="-DOVERLAY_CONFIG=overlay-tls.conf"
|
D | README.rst | 36 Enabling TLS support 39 Enable TLS support in the sample by building the project with the 40 ``overlay-tls.conf`` overlay file enabled using these commands: 45 :conf: "prj.conf overlay-tls.conf" 49 An alternative way is to specify ``-DEXTRA_CONF_FILE=overlay-tls.conf`` when 87 You can verify TLS communication with a Linux host as well. Just use the
|
/Zephyr-latest/samples/net/sockets/echo_server/ |
D | README.rst | 49 - :file:`overlay-tls.conf` 50 This overlay config enables support for TLS. 90 Enabling TLS support 93 Enable TLS support in the sample by building the project with the 94 ``overlay-tls.conf`` overlay file enabled, for example, using these commands: 99 :conf: "prj.conf overlay-tls.conf" 103 An alternative way is to specify ``-DEXTRA_CONF_FILE=overlay-tls.conf`` when 137 You can verify TLS communication with a Linux host as well. See 139 on how to test TLS with Linux host samples.
|
/Zephyr-latest/tests/modules/thrift/ThriftTest/ |
D | overlay-tls.conf | 13 # tls socket (accept): 1 15 # tls sockets (client, server): 2 19 # TLS configuration
|
/Zephyr-latest/samples/net/sockets/websocket_client/ |
D | README.rst | 37 Enabling TLS support 40 Enable TLS support in the sample by building the project with the 41 ``overlay-tls.conf`` overlay file enabled using these commands: 46 :conf: "prj.conf overlay-tls.conf" 50 An alternative way is to specify ``-DEXTRA_CONF_FILE=overlay-tls.conf`` when 95 not support TLS.
|