[pycrypto] Docs/code mis-match - not specifying IV fails
hugh.macdonald at nvizible.com
Tue Jan 7 09:43:03 PST 2014
I've just been trying to figure out why some code of mine broke after an
update from 2.0.1 to 2.6.1, and found that I hadn't been passing an IV into
AES.new() (using MODE_CFB).
Previously, it was happy with this, and, according to the docs here (
https://www.dlitz.net/software/pycrypto/api/current/), "It is optional and
when not present it will be given a default value of all zeroes."
Looking at the code that throws the exception (
163), it doesn't allow for doing what the docs suggest it will.
I'm not sure whether I've either misunderstood something or which of the
two is wrong, but I thought I'd at least flag it for discussion...
D I S C L A I M E R : This email and any files transmitted with it are
intended solely for the intended addressee, and may contain confidential
information or material protected by law, copyright or other legislation.
If you have received this message in error, please return it to the sender
or notify the sender by calling +44 (0)20 3167 3860, and immediately and
permanently delete it. You should not copy it or use it for any purpose,
nor disclose its contents to any other person. Only the intended recipient
may place any reliance upon it. Nvizible Limited accepts no responsibility
or liability for emails sent by its employees or personnel which are not
sent in the course of its business or that of its clients.
Nvizible Limited, 8/9 Carlisle Street, London W1D 3BP . Registered in
England & Wales with Company Number: 6900121
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pycrypto