Johannes Baeuer wrote:
> Why would a 16 byte block need to be padded by one byte to 17 bytes?
Is it really not immediately obvious?
No encrypted output for one or more bytes of input can be less than 16
bytes. Thus the smallest possible output sequence is 16-bytes. The number of
possible encrypt
Johannes Bauer wrote:
> > padding
> Why would a 16 byte block need to be padded by one byte to 17 bytes?
If you see an arbitary block of 16 bytes data it's hard to tell
immediately whether the last byte is a padding element that should be
removed or part of the content. That is why padding is _alw
Johannes Bauer wrote:
Hello list,
I'm having trouble with the openssl enc feature. This here:
echo -n '0123456789abcde' | openssl enc -aes128 -nosalt -K
00112233445566778899aabbccddeeff -iv | wc -c
(encoding 15 characters) results in one result block being gen
Johannes Bauer wrote on Friday, May 07, 2010 11:40:
> (encoding 15 characters) results in one result block being generated ...
> when encrypting a full block ...
> Then two result blocks are generated ...
PKCS#5 padding appends 1..blocksize padding bytes.
--
Peter-Michael Hager - acm senior - H
Original-Nachricht
>
> padding
Why would a 16 byte block need to be padded by one byte to 17 bytes?
Regards,
Johannes
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
_
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }
padding
On Fri 07/05/10 10:39 AM , "Johannes Bauer" jb@gmx.de sent:
Hello list,
I'm having trouble with the openssl enc feature. This here:
echo -n '0123456789abcde' | openssl enc -aes128 -nosalt -K
00112233445566778899aab
