Hi,
I’m hitting an assert at line 197 in secblock.h when using AES-CBC
encryption with 256 bit key. It started with occasional failure when
generating random keys and I could not find out what’s causing the
problem, because I needed many attempts to get repro. Later on when I
had a few keys
I forgot - I'm using CryptoPP 5.6.1
On Feb 21, 4:43 pm, User56784 r.ja...@comcast.net wrote:
Hi,
I’m hitting an assert at line 197 in secblock.h when using AES-CBC
encryption with 256 bit key. It started with occasional failure when
generating random keys and I could not find out what’s
I have tried with CRYPTOPP_BOOL_ALIGN16_ENABLED 0, but encryption/
decryption stopped working completely.
Perhaps this flag can be used only on big-endians to make bytes
ordered correctly.
But thanks for info, it definitely must be some issue with allocator/
deallocator, because in deallocator
You are absolutely right that using random IV during encryption and
then another random IV during decryption will lead to garbage. What
you have to do is to send your random IV along with encrypted text.
Usually you put IV at the beginning. For example:
IV = 60ca
cipher = f576ab
you send
to determine length of the password for brute force attack. If you
have XML file around 50 kB in size, the length for encryption will be
anywhere from 49152 B - 53248 B (multiple of 4096).
On Feb 26, 6:12 am, Robert Bielik robert.bie...@modularstreams.com
wrote:
On 26 Feb, 04:17, User56784 r.ja
