Lines Matching refs:Rijndael

4  * Pure-PHP implementation of Rijndael.
16  * Not all Rijndael implementations may support 160-bits or 224-bits as the block length / key length.  mcrypt, for example,
18  * {@link http://csrc.nist.gov/archive/aes/rijndael/Rijndael-ammended.pdf#page=10 Rijndael-ammended.pdf#page=10} defines the
21  * {@link http://csrc.nist.gov/archive/aes/rijndael/Rijndael-ammended.pdf#page=44 Rijndael-ammended.pdf#page=44}:
33  *    $rijndael = new \phpseclib3\Crypt\Rijndael('ctr');
63  * Pure-PHP implementation of Rijndael.
67 class Rijndael extends BlockCipher
73      * \phpseclib3\Crypt\Rijndael determines automatically whether mcrypt is useable
178      * Note: phpseclib extends Rijndael (and AES) for using 160- and 224-bit keys but they are officially not defined
182      *       That said, if you want be compatible with other Rijndael and AES implementations,
212      * Rijndael supports five different key lengths
340         // Various Platforms" suggests that performs enhanced implementations are described in Rijndael-ammended.pdf.
341         // Rijndael-ammended.pdf#page=20, "Implementation aspects / 32-bit processor", discusses such an optimization.
518         // Each number in $rcon is equal to the previous number multiplied by two in Rijndael's finite field.
541         // see Rijndael-ammended.pdf#page=44
544         // shift offsets for Nb = 5, 7 are defined in Rijndael-ammended.pdf#page=44,
546         // shift offsets for Nb = 4, 6, 8 are defined in Rijndael-ammended.pdf#page=14,
581         // according to <http://csrc.nist.gov/archive/aes/rijndael/Rijndael-ammended.pdf#page=23> (section 5.3.3),
659             // according to <http://csrc.nist.gov/archive/aes/rijndael/Rijndael-ammended.pdf#page=19> (section 5.2.1),