Bug in decryption algorithm? about aes HOT 10 CLOSED

hi, can you help adding a full reproduceable example, eg a report or a class, perhaps add it on http://gist.github.com or in a public repository?

from aes.

Sure, here is the class I have created from your AES library, as well as a sample report that calls this class.

https://gist.github.com/haimat/cd1465f09b65aab731279253340d6f1d

from aes.

I don't have the environment any more, but I suggest checking the encoding and possibly padding?

from aes.

I tried to find an enconding problem, but didn't work out.
But I am far from being a crypto expert :(

Anything I could do for you guys to check that out with the working example I have posted?

from aes.

Hi, the gist you posted do not contain code for zdkk_rijndael_utility. Can you post that as well for checking the issue?

One more question, are you trying to recreate the utility classes yourself rather than importing from GIT?

from aes.

Ohh yes, sure, sorry for that.
I have updated the Gist and added the code for the ZDKK_RIJNDAEL_UTILITY class.

from aes.

from aes.

The method lr_aes_util->decrypt_xstring returns the following xstring in lv_x_result:
ACF617EDAB61368AA977014DB821C59E

from aes.

Hi the issue is the parameter p_encdat is converting all the data to upper case causing the issue.

I corrected the same and posted in this gist
https://gist.github.com/raviandela/6f4b1c85eb493f0274f7462e8ef1e984

Output I got is : "0075266945"

Attached is the output.

from aes.

Thank you very much, that's it!

from aes.