aes128-cbc encrypt result differ from openssl command line? about tiny-aes-c HOT 4 CLOSED

Is the OpenSSL version including a null terminator?

Edit: Nevermind. It's because you have the wrong size for 'in'. You specify 13 bytes but give it a size of 16, so you're passing three random bytes into the AES encrypt routine.

Edit 2: Same for 'key' and 'iv'.

from tiny-aes-c.

OPENSSL uses PKCS7 padding.

PKCS7 padding does not pad with zeros; instead, it pads with the remainder. so, if there are 4 bytes missing to make it modulus 16; the input will be padded with 4 bytes containing the number 4. PKCS7 also requires at least ONE padding byte; so if your input length is exactly modulus 16 - you need to add 16 bytes, containing the value 16.

i implemented AES-128/192/256 working against openSSL (within PHP) initially based on the code in this repository; but in order to support 192/256 i had to make some minor changes in addition to dealing with PKCS7 padding.

http://ardiri.com/blog/utls_defining_lightweight_security_for_iot_part_5

from tiny-aes-c.

The fork by triangulum-com-au implements PKCS7 padding (look at the tests). I've used it with success.

from tiny-aes-c.

Thanks to @namreeb @ardiri @wvengen helps , I did not consider the padding at the first time and the program appears different result. Thank you!

from tiny-aes-c.