<?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>NCS 3.3.0 HMAC-SHA512 with image encryption</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128511/ncs-3-3-0-hmac-sha512-with-image-encryption</link><description>I have a nRF54L15 firmware built on NCS v3.0.1, with image encryption enabled in mcuboot. Firmware needs to be updated to new version built on NCS 3.3.0. 
 In NCS 3.0.1, image encryption used HMAC-SHA256, while on the 3.3.0, HMAC-SHA512 is also supported</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Jun 2026 12:17:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128511/ncs-3-3-0-hmac-sha512-with-image-encryption" /><item><title>RE: NCS 3.3.0 HMAC-SHA512 with image encryption</title><link>https://devzone.nordicsemi.com/thread/568255?ContentTypeID=1</link><pubDate>Mon, 22 Jun 2026 12:17:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:460d8630-885b-43a5-b267-bb94c4498d58</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;It looks like we decided to standardise on&amp;nbsp;SHA512 for encryption as well do avoid having to include support for both sha256 and sha512 in the bootloader crypto library (by default), but removing the option of using SHA 256 seems like a breaking change. I will need to check internally to confirm the details. In the meantime, can you confirm that it works if you temoparly remove the &amp;quot;imgtool_encrypt_extra_args&amp;quot; assignment in the signing script?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;
&lt;p&gt;EDIT: turns out there was already an open PR to address this:&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/pull/28618"&gt;https://github.com/nrfconnect/sdk-nrf/pull/28618&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;EDIT2: PR above was a back port to 3.1 branch and was closed. Fix is merged on main:&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/commit/0caabb0d090de9ae3d4e85744ac26a739b26fc37"&gt;https://github.com/nrfconnect/sdk-nrf/commit/0caabb0d090de9ae3d4e85744ac26a739b26fc37&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>