[tahoe-lafs-trac-stream] [pycryptopp] #46: Add combined AES+XSalsa20 cipher module

pycryptopp trac at tahoe-lafs.org
Sat Aug 11 04:24:26 UTC 2012


#46: Add combined AES+XSalsa20 cipher module
-------------------------------------------------+-------------------------
Reporter:  randombit                             |          Owner:
    Type:  enhancement                           |  from_pycon
Priority:  major                                 |         Status:  new
 Version:  0.5.19                                |      Milestone:  0.7.0
Keywords:  xsalsa20 aes combiner design-review-  |     Resolution:
  needed                                         |  Launchpad Bug:
-------------------------------------------------+-------------------------

Comment (by zooko):

 Replying to [comment:12 zooko]:
 >
 > • I want benchmarks of XSalsa20⊕AES-128 compared to XSalsa20⊕AES-256.

 Here they are. This script measures the time to crypt a 10 MB string and
 divides by 10,000,000 to get a time per byte.

 On a fast amd64 workstation/server:

 https://tahoe-lafs.org/buildbot-pycryptopp/builders/Kyle%20OpenBSD-
 amd64/builds/119/steps/bench/logs/stdio

 XSalsa20: 2 nanoseconds per byte crypted
 AES-128:  5 nanoseconds per byte crypted
 AES=256:  7 nanoseconds per byte crypted

 On a weak, low-power, cheap ARM device:

 https://tahoe-lafs.org/buildbot-pycryptopp/builders/francois-
 ts109-armv5tel%20syslib/builds/109/steps/bench/logs/stdio

 XSalsa20: 138 nanoseconds per byte crypted
 AES-128:  264 nanoseconds per byte crypted
 AES-256:  339 nanoseconds per byte crypted

 So the time to crypt a 1 GB file with XSalsa20⊕AES-128 on that tiny ARM
 device would be about 400 seconds, and the time to crypt it with
 XSalsa20⊕AES-256 would be about 475 seconds.

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



More information about the tahoe-lafs-trac-stream mailing list