<?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>Crypto AES-ECB padding byte mechanism.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62861/crypto-aes-ecb-padding-byte-mechanism</link><description>Hi Team, 
 
 If we send 20 bytes of data to AES-ECB 128 bit (CC310/ mbed TLS) Crypto engines for Encryption/Decryption due to bytes padding, how many bytes it will become as final output. Could any body confirm on this one. 
 
 Regards, 
 Srinivas.V</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Jun 2020 15:09:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62861/crypto-aes-ecb-padding-byte-mechanism" /><item><title>RE: Crypto AES-ECB padding byte mechanism.</title><link>https://devzone.nordicsemi.com/thread/256255?ContentTypeID=1</link><pubDate>Mon, 22 Jun 2020 15:09:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e4fad372-6068-4e1f-8e54-66a25f7e27ba</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Srinivas,&lt;/p&gt;
&lt;p&gt;The output is a multiple of 16 bytes, so there will be 12 padding bytes and a total of 32 bytes.&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>