Hello,
> On Wed, Oct 18, 2006 at 11:35:13AM +0200, Marek Marcola wrote:
> > Hello,
> > > the block size is always the same as the key length in AES (and the most
> > > block
> > > ciphers, I think). You are using 128-AES -> 128 bits key == 16 bytes
> > > block size
> > > (q.e.d).
> > Not exac
On Wed, Oct 18, 2006 at 11:35:13AM +0200, Marek Marcola wrote:
> Hello,
> > the block size is always the same as the key length in AES (and the most
> > block
> > ciphers, I think). You are using 128-AES -> 128 bits key == 16 bytes block
> > size
> > (q.e.d).
> Not exactly:
>
> AES128: block
Hello,
> the block size is always the same as the key length in AES (and the most
> block
> ciphers, I think). You are using 128-AES -> 128 bits key == 16 bytes block
> size
> (q.e.d).
Not exactly:
AES128: block_size: 16 bytes, key_size: 16 bytes
AES192: block_size: 16 bytes, key_size: 24 by
Hi,
the block size is always the same as the key length in AES (and the most block
ciphers, I think). You are using 128-AES -> 128 bits key == 16 bytes block size
(q.e.d).
Good luck,
Sebastian
Eric S. Eberhard wrote:
Kyle,
Thank you ... I thought I was missing something (actually the
behav
Kyle,
Thank you ... I thought I was missing something (actually the
behavior told me what you told me, I just wanted to confirm it was
correct). I won't actually use ECB, it was randomly selected from
the test file ...
A follow-up then ... if I have 37 bytes I would call Update twice and
F
OpenSSL does not store the plaintext size in block protocol usage.
That's an application-layer issue.
ECB mode, by the way, is REALLY discouraged.
Padding doesn't come into play until the second-to-last and last
blocks. You should get 16*(3 blocks of data +1 block for the
EncryptFinal()) == 64
