>
> As noted in the comment, that test is currently expected to fail.
>
> sorry, I missed that comment about the expected behavior.

a similar test passes in SpooledEF, but only because I coded around the
issue (probably very inefficiently).


> There's something wrong with the way in which I'm incrementing my counter.
>

ah, ok. its too bad that pyCrypto documentation is not so great with
respect to AES_CTR. its on their bug-track as something to fix (the
documentation). https://bugs.launchpad.net/pycrypto/+bug/899818  maybe if
it gets up-voted enough it will be elaborated / fixed.

frankly, I'm confused by what is going on. the function ctr given as
AES.new(..., counter=ctr,...) only appears to ever be called once by the
pycrypto internals.