:orphan: .. title:: CONFIG_TLS_CREDENTIAL_FILENAMES .. kconfig:: CONFIG_TLS_CREDENTIAL_FILENAMES CONFIG_TLS_CREDENTIAL_FILENAMES ############################### *Specify TLS credential filenames* Type: ``bool`` Help ==== .. code-block:: none Allows clients of the socket APIs to specify filenames of security certificates and private keys to use during subsequent TLS/SSL negotiations. The secure files will have been previously provisioned to the device's secure file system; eg, via a vendor tool or by executing a separate binary. This option is currently only available for secure socket offload devices. Direct dependencies =================== \ :kconfig:`NET_SOCKETS_OFFLOAD ` && \ :kconfig:`TLS_CREDENTIALS ` && \ :kconfig:`NETWORKING ` *(Includes any dependencies from ifs and menus.)* Defaults ======== No defaults. Implicitly defaults to ``n``. Kconfig definition ================== At ``/net/lib/tls_credentials/Kconfig:17`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``/Kconfig:39`` → ``/net/Kconfig:89`` → ``/net/lib/Kconfig:32`` Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → Network Libraries → TLS credentials management .. code-block:: kconfig config TLS_CREDENTIAL_FILENAMES bool "Specify TLS credential filenames" depends on NET_SOCKETS_OFFLOAD && TLS_CREDENTIALS && NETWORKING help Allows clients of the socket APIs to specify filenames of security certificates and private keys to use during subsequent TLS/SSL negotiations. The secure files will have been previously provisioned to the device's secure file system; eg, via a vendor tool or by executing a separate binary. This option is currently only available for secure socket offload devices. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*