[tahoe-lafs-trac-stream] [pycryptopp] #92: python-level time padding

[pycryptopp]

#92: python-level time padding
-------------------+---------------------
Reporter:  zooko   |          Owner:
    Type:  defect  |         Status:  new
Priority:  major   |      Milestone:
 Version:  0.5.29  |     Resolution:
Keywords:          |  Launchpad Bug:
-------------------+---------------------

Comment (by zooko):

 Replying to [comment:1 davidsarah]:
 >
 > "Using a separate thread" does not guarantee parallel execution.

 Good point — thanks!

 We could make it so that if the execution is not sufficiently parallel,
 then the failure mode is abort rather than leak-secrets.

 However, that would be very unsatisfying. Users would either stop using
 the software, or they would figure out how to automatically retry in
 response to abort, thus moving the failure mode back into the "leak-
 secrets" side. ☺

 I should mention that my motivation for this is mostly to avoid C/C++/asm
 code in order to have easier packaging, deployment, and portability.
 Wouldn't it be great if you could do all of your crypto in pure Python?

-- 
Ticket URL: <https://tahoe-lafs.org/trac/pycryptopp/ticket/92#comment:2>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>