diff options
Diffstat (limited to 'pipermail/pycrypto/attachments/20120626/86c9f685/attachment-0001.html')
-rw-r--r-- | pipermail/pycrypto/attachments/20120626/86c9f685/attachment-0001.html | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/pipermail/pycrypto/attachments/20120626/86c9f685/attachment-0001.html b/pipermail/pycrypto/attachments/20120626/86c9f685/attachment-0001.html new file mode 100644 index 0000000..52380a9 --- /dev/null +++ b/pipermail/pycrypto/attachments/20120626/86c9f685/attachment-0001.html @@ -0,0 +1,12 @@ +<tt> +<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br> +> Up to pycrypto 2.5, when no iv was provided to new() a string of zeroes was<br><br> +> automatically used.<br><br> +> Depending on your application, that may or may not be a problem. It is wiser<br><br> +> to always make iv explicit.<br><br> +<br><br> +</div>Which explains why my 'old' code failed. Thanks.<br><br> +Needing both key and iv... It sounds like asking for two keys to unlock a box?<br><br> +Is that the idea?<br></blockquote><div><br>Well, an important difference is that the IV is not a secret, so it's not really a key,<br>just a way to randomize the key stream. <br></div></div><br> + +</tt> |