[pycrypto] Issue with the new random.choice() unit test

Lorenz Quack don at amberfisharts.com
Wed Jan 5 13:36:25 CST 2011


Hey,

I now also took a look at AllOrNothing.
It was using long_to_bytes with out specifing how many bytes it wants returned.
Requesting a multiple of the block_size fixed the failing test.
A few rows below it looked like the same could have happened with the key.
I also fixed that.
I did not review the code any further.

patch is attached.

Cheers,
//Lorenz


On 01/05/2011 08:14 PM, Lorenz Quack wrote:
> [...]
> I didn't take a look at AllOrNothing yet.
>
> Cheers,
> //Lorenz
>
>
> On 01/05/2011 02:01 PM, Thorsten Behrens wrote:
>> Do you have any ideas on the ailing AllOrNothing.py and random.sample on
>> Python 2.1? I haven't dug into those yet beyond
>> noting that they have issues, exposed by the new unit tests.
>>
>> Yours
>> Thorsten
>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: AllOrNothing.patch
Url: http://lists.dlitz.net/pipermail/pycrypto/attachments/20110105/0f806abb/attachment.txt 


More information about the pycrypto mailing list