<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Unable to change MBEDTLS_CFG_FILE in NCS 3.2</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127259/unable-to-change-mbedtls_cfg_file-in-ncs-3-2</link><description>With NCS 3.2.1 I can&amp;#39;t make use of custom mbed TLS config headers anymore, the MBEDTLS_CFG_FILE KConfig option always get overwritten. Previously setting CONFIG_CUSTOM_MBEDTLS_CFG_FILE=y would allow for overriding the config header. The documentation</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 05 Mar 2026 18:00:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127259/unable-to-change-mbedtls_cfg_file-in-ncs-3-2" /><item><title>RE: Unable to change MBEDTLS_CFG_FILE in NCS 3.2</title><link>https://devzone.nordicsemi.com/thread/562678?ContentTypeID=1</link><pubDate>Thu, 05 Mar 2026 18:00:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:646966cb-2f41-4233-b0f0-6be7961490c9</guid><dc:creator>timonsku</dc:creator><description>&lt;p&gt;Thanks for clarifying, thats what I figured after reading further into the upstream Zephyr plans on this and what happened in mbed TLS itself. It wasn&amp;#39;t quite clear that only portions of mbed TLS has changed upstream and that this reflects those changes by the upstream project.&lt;br /&gt;When I read &amp;quot;crypto APIs&amp;quot; in my head that extended to just refer to &amp;quot;mbed TLS&amp;quot; as in the past it was just &amp;quot;the crypto library&amp;quot; in projects.&lt;br /&gt;I was able to resolve not being able to set the custom header. There was another config (CONFIG_MBEDTLS_BUILTIN) set to =y elsewhere that was a dependency of =n in order to be able to set a custom config&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to change MBEDTLS_CFG_FILE in NCS 3.2</title><link>https://devzone.nordicsemi.com/thread/562608?ContentTypeID=1</link><pubDate>Thu, 05 Mar 2026 07:26:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d5a84924-1089-4fc2-be1a-386a4fbd2e22</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am sorry for being confusing. It is not that mbed TLS is being removed, but the legacy mbedTLS crypto APIs will be removed. This is removed from mbedTLS itself in &lt;a href="https://github.com/Mbed-TLS/mbedtls/releases/tag/mbedtls-4.0.0"&gt;mbed TLS 4.0&lt;/a&gt;, so as a consequence, support will be removed when we integrate mbed TLS 4.0.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to change MBEDTLS_CFG_FILE in NCS 3.2</title><link>https://devzone.nordicsemi.com/thread/562595?ContentTypeID=1</link><pubDate>Thu, 05 Mar 2026 00:28:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6fbbb041-f206-4b6c-b8a4-a71e22ed2a9a</guid><dc:creator>timonsku</dc:creator><description>&lt;p&gt;Especially as mbed TLS seems to still be very much needed. The PSA APIs would not cover X.509 or TLS related functionality. From the mbed TLS project:&amp;nbsp;&lt;a id="" href="https://github.com/Mbed-TLS/mbedtls/blob/development/docs/4.0-migration-guide.md"&gt;https://github.com/Mbed-TLS/mbedtls/blob/development/docs/4.0-migration-guide.md&lt;/a&gt;&lt;br /&gt;&amp;quot;Mbed TLS has been split between two products: TF-PSA-Crypto for cryptography, and Mbed TLS for X.509 and (D)TLS.&amp;quot;&lt;br /&gt;Which means needing to configure mbed TLS is still necessary but right now I get circular dependencies with anything related to setting a custom header file for mbed TLS.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to change MBEDTLS_CFG_FILE in NCS 3.2</title><link>https://devzone.nordicsemi.com/thread/562594?ContentTypeID=1</link><pubDate>Wed, 04 Mar 2026 23:41:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2fa1170f-522e-42ca-8527-b7718ffbe1c8</guid><dc:creator>timonsku</dc:creator><description>&lt;p&gt;Just to be clear, when you say legacy mbed TLS crypto APIs that means the entirety of mbed TLS is deprecated?&lt;br /&gt;It is not quite clear from the docs if that just means certain parts of it or all of it. mbed TLS is still around in the SDK and there are not deprecation warnings when you make use of mbed TLS functions so its a bit confusing whether its just unsupported now or going to be fully deprecated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to change MBEDTLS_CFG_FILE in NCS 3.2</title><link>https://devzone.nordicsemi.com/thread/562567?ContentTypeID=1</link><pubDate>Wed, 04 Mar 2026 15:11:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:482b4a3a-5179-4448-8649-71cb72f3c442</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;As you note, legacy mbed TLS crypto API&amp;#39;s have been deprecated for a while, and will soon be removed. I&amp;nbsp;would strongly advice that you migrate to PSA crypto APIs. Regarding samples you should refer to the &lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/crypto.html"&gt;crypto samples under nrf&lt;/a&gt;. I do not believe we have a specific migration guide for migrating from legacy APIs to PSA crypto APIs, but I suggest referring to the samples to see how PSA crypto is used.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>