At the very least, you are using differing initialization vectors (IV). The .Net code uses the key for IV. private static AesCryptoServiceProvider GetProvider(byte[] key) { //Set up the encryption objects AesCryptoServiceProvider result = new AesCryptoServiceProvider(); byte[] RealKey = Encryptor.GetKey(key, result); result.Key = RealKey; result.IV = RealKey; return result; } and private static byte[] GetKey(byte[] suggestedKey, … Read more
Official document of Crypto++ AES is a good start. And from my archive, a basic implementation of AES is as follows: Please refer here with more explanation, I recommend you first understand the algorithm and then try to understand each line step by step. #include <iostream> #include <iomanip> #include “modes.h” #include “aes.h” #include “filters.h” int … Read more
There is no support in any of the Sun JCE providers for anything other than Rijndael with the 128-bit blocksize: this is the AES algorithm. To get rijndael with the 256-bit blocksize you will have to go somewhere else. I suggest the Bouncycastle java library. The RijndaelEngine class has a constructor that accepts a block … Read more
Usually, you will be intending to call AES_ctr128_encrypt() repeatedly to send several messages with the same key and IV, and an incrementing counter. This means you need to keep track of the ‘ivec’, ‘num’ and ‘ecount’ values between calls – so create a struct to hold these, and an initialisation function: struct ctr_state { unsigned … Read more
Be sure to use the same parameters which seem to be AES with CBC mode with iv, PKCS5Padding (actually PKCS#7) padding and a 16-byte (128-bit) key. PKCS#5 padding and PKCS#7 padding are essentially the same, sometimes for historic reasons PKCS#5 padding is specified for use with AES but the actual padding is PKCS#7. Make sure … Read more
Your Order for encrypt: getBytes, encrypt, encode, toString Your Order for decrypt(Wrong*): getBytes, decrypt, decode, toString Two problems: As someone already mentioned you should reverse the order of operations for decryption. You are not doing that. encrypt gives you 16 bytes, encode 24 bytes, but toString gives 106 bytes. Something to do with invalid chars … Read more
When you encrypt a string with AES, you get an array of bytes back. Trying to convert those bytes directly to a string (new String(cipher.doFinal(plaintextBytes))) will cause all sorts of problems. If you require the output from your encryption method to be a string, then use Base64 rather than attempting a direct conversion. In your … Read more
If you take user input for the password make sure to read this answer. You should take a look at: CipherInputStream and CipherOutputStream. They are used to encrypt and decrypt byte streams. I have a file named cleartext. The file contains: Hi, I’m a clear text. How are you? That’s awesome! Now, you have an … Read more
Edit: As written in the comments the old code is not “best practice”. You should use a keygeneration algorithm like PBKDF2 with a high iteration count. You also should use at least partly a non static (meaning for each “identity” exclusive) salt. If possible randomly generated and stored together with the ciphertext. SecureRandom sr = … Read more
Warning: This answer contains code you should not use as it is insecure (using SHA1PRNG for key derivation and using AES in ECB mode) Instead (as of 2016), use PBKDF2WithHmacSHA1 for key derivation and AES in CBC or GCM mode (GCM provides both privacy and integrity) You could use functions like these: private static byte[] … Read more