Closed FrankFang closed 1 year ago
keySize
seems not to be a cfg field for Cipher in CryptoJS (CryptoES keeps consistent with CryptoJS).
The keySize
is set in sub cipher's definition body,
and passed into kdf.execute before the cipher's instance merging cfg:
The cipher
here in cipher.keySize
is a constructor like CryptoJS.algo.AES
, not a instance with cfg merged.
I tracked it in debug mode, when I passed a keySize: 16
, it seemed still keySize 8(The value set in AES) is passed into kdf.execute. Will the keySize passed into cfg affects the result in your case?
(All this are tested in CryptoJS and CryptoES has same logic with it.)
It makes sense.