DO NOT USE THIS CODE IN PRODUCTION
This is an educational example of how to use the Java and C AES libraries originally from a Stackoverflow Answer. This code is not safe and it is not an example of how to securely use AES.
Many additional factors will need to be considered when buidling a secure system that uses AES, for example: How to properly use IVs; Block cipher modes and their properties; Secure key generation; Key distribution; message and author authentication; and many more factors besides.
At a minimum, you'll want to go through and make sure you understand the Cryptography Engineering Book, and are aware of any current security issues reported about the library you are using.
If you don't already
- Know how to use and import a C library
- Understand what IVs are and how they should be used
- Understand the difference between block size and key size
- Know that Libmcrypt is deprecated and why you still want to use it
Do not use this code.
The library used in the C example, Libmcrypt, is deprecated. It'll work, but for most use cases, you'll want to use a more modern cryptographic library. Current recommeded best practice would point to NaCl and its close cousin Libsodium Which have been extensively tested, audited and only allow current best practice algorithms and methods.
As commented below there are a couple of issues with the code. It was written to be a quick example, not a reference and as such handles its data badly.
@rwst comments:
[...] the buffer, when decrypted, certainly won't have a 0 byte at the end, so printing it as is, even if it is printable, will get another unexpected result.
You should know what this means and how to handle the case where the decrypted data doesn't include a terminating null character.
You should be able to realise that the C code currently encrypts memory outside of the plaintext
string since the buffer length is greater than the string length (and why the Java string is padded). If this isn't clear to you, don't use this code.
If you are getting this error and do not know what it means or how to resolve it, STOP. YOU DO NOT KNOW ENOUGH TO BE WRITING SECURITY SOFTWARE. I will not help you to resolve this issue, to discourage you from continuing with this code sample.
I'm sorry to be so blunt, and don't want to discourage you from learning C programming or software security, which are both very rewarding, but you should start your journey with a simpler example. There are many great resources for you. I'd recommend starting with The C Programming Language. It's old now, and has some questionable examples and practices, but it's still a great start. There is also a communtiy list of resources on Stackoverflow to get you started.
If you want to learn more about how to use cryptography correctly, a good start is Cryptography Engineering. You should also use modern, independently audited and tested libraries like NaCl or Libsodium.
I've got an app with microprocessors using C talking to Android using Java. I am using AES-128, but am trying to make keys more complex. Examples I have seen use the Base64 character set in keys, but I am trying to use a full 128 bit key, any value (apart from 0x00 bytes, which I am avoiding for C reasons). In my tests, I managed to get a message from Java to C devices and decrypt it properly. The reply does not decrypt properly in the Java code. If I turn off the top bit (sign bit) in all 16 bytes, it works. This sort of turns my attempt at full AES 128 into a sort of AES 112. Is there an Android Java function that will get me round this?