https://devzone.nordicsemi.com/f/nordic-q-a/10541/question-about-asymmetric-encryption-dfuWe have created a firmware and encrypted it with a private key and made it public. When we download it to the chip it&#39;s decrypted with a public key stored in the chip. Right? What adnventages does it offer vs. standart symmetric encryption?en-USTelligent Community 13Mon, 30 Nov 2015 12:27:20 GMThttps://devzone.nordicsemi.com/thread/39215?ContentTypeID=1Mon, 30 Nov 2015 12:27:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:be264a9f-6e90-462f-8a0d-620a0ab1fba8Vidar Berg<p>DFU signing ensures that an image is received from a trusted source, but doesn&#39;t encrypt it as Wojtek mentioned. The advantage with asymmetric over symmetric signing is that it&#39;s safer because only the public key will be stored on the nRF device, while the drawback is increased complexity.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/39214?ContentTypeID=1Sun, 29 Nov 2015 23:25:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0a78bd9e-9296-43b7-ab3b-9bbd96051668Wojtek<p>If you are using signing tools from newest SDK, it doesn&#39;t encrypt your firmware! If I understand correctly, there is only a checksum (sha-256) of the firmware, that is signed (by your private key) and verified on the chip (by verification - public key). there is no encryption there. So if you are worrying about decompilation of firmware, that is not the solution. It only protects your chip from unauthorized DFU updates (which may brick your device or something)</p><div style="clear:both;"></div>