[tahoe-lafs-trac-stream] [pycryptopp] #40: xsalsa20 wrapper
pycryptopp
trac at tahoe-lafs.org
Tue Feb 7 05:28:31 UTC 2012
#40: xsalsa20 wrapper
-----------------------------------+------------------------
Reporter: dragonxue | Owner: xue yu
Type: enhancement | Status: new
Priority: major | Milestone: 0.6.0
Version: 0.5.19 | Resolution:
Keywords: xsalsa20 review-needed | Launchpad Bug:
-----------------------------------+------------------------
Comment (by warner):
I've updated my branch with some improvements:
* add a power-on self-test
* fix the same wrong-length-IV bug that was present in the AES code (#70)
I skimmed xsalsamodule.cpp looking for memory problems, and nothing jumped
out at me.
One question came to mind, though: do we want this to be named
"{{{xsalsa}}}", or would "{{{XSalsa20}}}" be better? (Or even
"{{{Salsa20}}}"? I'm not sure exactly what the "X" means, and calling it
Salsa20 would distinguish it from the reduced-round Salsa12/Salsa08
variants).
--
Ticket URL: <http://tahoe-lafs.org/trac/pycryptopp/ticket/40#comment:8>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>
More information about the tahoe-lafs-trac-stream
mailing list