[tahoe-lafs-trac-stream] [pycryptopp] #40: xsalsa20 wrapper

[pycryptopp]

#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 zooko):

 Brian:

 Thank you for doing this work!

 > 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).

 The 'X' denotes an incompatible new variant of the algorithm, with a
 192-bit nonce instead of 64-bit (so that implementors can pick random
 nonces instead of maintaining a counter). See the paper on
 http://cr.yp.to/snuffle.html denoted "[xsalsa]". We should include 'X' in
 the name. I agree about the '20', so let's name it 'XSalsa20'.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/pycryptopp/ticket/40#comment:10>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>