:orphan:

.. title:: TLS_CREDENTIAL_FILENAMES

.. option:: CONFIG_TLS_CREDENTIAL_FILENAMES

*Specify TLS credential filenames*

Type: ``bool``

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.

Direct dependencies
===================

\ :option:`NET_SOCKETS_OFFLOAD <CONFIG_NET_SOCKETS_OFFLOAD>` && \ :option:`TLS_CREDENTIALS <CONFIG_TLS_CREDENTIALS>` && \ :option:`NETWORKING <CONFIG_NETWORKING>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definition
==================

.. highlight:: kconfig

At ``subsys/net/lib/tls_credentials/Kconfig:17``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:37`` → ``subsys/net/Kconfig:89`` → ``subsys/net/lib/Kconfig:32``

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → Network Libraries → TLS credentials management

.. parsed-literal::

    config TLS_CREDENTIAL_FILENAMES
    	bool "Specify TLS credential filenames"
    	depends on \ :option:`NET_SOCKETS_OFFLOAD <CONFIG_NET_SOCKETS_OFFLOAD>` && \ :option:`TLS_CREDENTIALS <CONFIG_TLS_CREDENTIALS>` && \ :option:`NETWORKING <CONFIG_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.)*