Lines Matching refs:_encryptBlock

25  * # phpseclib's four different _encryptBlock() implementations
27  * When using Blowfish as an encryption algorithm, _encryptBlock() is called 9 + 512 +
30  * Each of the first 9 calls to _encryptBlock() modify the P-array. Each of the next 512
31  * calls modify the S-boxes. The remaining _encryptBlock() calls operate on the plaintext to
33  * _encryptBlock() calls are highly optimized through the use of eval(). Among other things,
35  * have explained 2 of the 4 different _encryptBlock() implementations.
37  * With bcrypt things are a bit different. _encryptBlock() is called 1,079,296 times,
39  * _encryptBlock() isn't as beneficial because the P-array values are not constant. Well, they
40  * are constant, but only for, at most, 777 _encryptBlock() calls, which is equivalent to ~6KB
41  * of data. The average length of back to back _encryptBlock() calls with a fixed P-array is
42  * 514.12, which is ~4KB of data. Creating an eval()-optimized _encryptBlock() has an upfront
44  * data. Conseqeuently, bcrypt does not benefit from the eval()-optimized _encryptBlock().
46  * The regular _encryptBlock() does unpack() and pack() on every call, as well, and that can
50  * that, instead of passing strings to _encryptBlock(), you convert the string to an array of
51  * integers and then pass successive subarrays of that array to _encryptBlock. This, however,
57  * _encryptBlock() then the regular Blowfish does. That said, the Blowfish _encryptBlock() is
58  * basically just a thin wrapper around the bcrypt _encryptBlock(), so there's that.
60  * This explains 3 of the 4 _encryptBlock() implementations. the last _encryptBlock()
75  * constantly XOR'ing every _encryptBlock() parameter against the salt prior _encryptBlock()'s
87  * initial S-boxes, the initial P-array and the int-only _encryptBlock() implementation.