Bug #60705 [Opn->Nab]: rijndael iv problem
Edit report at https://bugs.php.net/bug.php?id=60705&edit=1
ID: 60705
Updated by: nikic@php.net
Reported by: erno dot kovacs at freemail dot hu
Summary: rijndael iv problem
-Status: Open
+Status: Not a bug
Type: Bug
Package: mcrypt related
Operating System: linux/windows
PHP Version: 5.3.8
Block user comment: N
Private report: N
New Comment:
As the last comments pointed, there's no bug here. AES-128, AES-192 and AES-256 are all handled
by Rijndael-128.
Previous Comments:
------------------------------------------------------------------------
[2014-03-04 15:35:41] narf at devilix dot net
This is not a bug, just something that is often confused.
AES does indeed have a fixed block size of 16 bytes and it is based on Rijndael. However, it is only
based on Rijndael-128, allowing different key sizes. Rijndael-192 and Rijndael-256 have different
block sizes and are NOT AES-compatible.
If you want to use AES-192, AES-256 with MCrypt, you just have to use Rijndael-128 with a 24 or
32-byte key respectively.
------------------------------------------------------------------------
[2012-10-02 12:28:11] miha dot vrhovnik at domenca dot com
Or maybe just the docs are foobar.
http://www.chilkatsoft.com/p/php_aes.txt
------------------------------------------------------------------------
[2012-10-02 10:01:56] miha dot vrhovnik at domenca dot com
I have the same problem as the reporter of this bug.
However the library used to decode the data is openssl 1.0.1c and I'd really doubt that they
messed this up.
------------------------------------------------------------------------
[2012-02-26 21:30:37] erno dot kovacs at freemail dot hu
AES blocksize is constant 16 bytes, so is the IV.
------------------------------------------------------------------------
[2012-02-26 21:27:16] erno dot kovacs at freemail dot hu
it seems you dont recognize the difference between the cipher block size and the input plaintext
data...
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=60705
--
Edit this bug report at https://bugs.php.net/bug.php?id=60705&edit=1
Thread (9 messages)