Hi, Is there any progress in the Threefish/Crypto++ implementation?
Thanks J.K. On Thursday, March 21, 2013 5:16:00 AM UTC+1, Collin Stocks wrote: > > I would be glad to write an interface to the existing Threefish code to be > incorporated into Crypto++, but I am not sure what the correct course of > action would be. > > Is there a version controlled version of the source I can fork, edit, and > submit a pull request (or similar process)? Or should I just download the > last release version (5.6.2), edit that, and then send a patch? > > Based on the release dates, it does not appear that there is a huge amount > of active development (as seems logical for a crypto library that must > always remain stable), and that the most recent release followed the > announcement of SHA-3 (with a suitable delay to ensure correct > implementation). With that in mind, is there a development version I should > create a patch for, or would the most recent release version be best? > > Finally, while I am at it, is there any interest in also wrapping Skein > (one of the finalists in the SHA-3 competition)? Personally, I have no need > for it, but I think there is value in providing different options for > people to use. However, if there is no interest, I probably won't bother > trying to add the extra functionality (on top of the wrapper for Threefish > that I plan to write already). > > -- Collin > > > On Wed, Mar 20, 2013 at 6:43 PM, Nick Pateman <[email protected] > <javascript:>> wrote: > >> If its available and you get it done please share. Sorry for not >> offering help. >> >> Sent from my iPad >> >> On 20 Mar 2013, at 22:06, "Collin Stocks" <[email protected] >> <javascript:>> wrote: >> >> I'm not really sure if this is the best place to post a suggestion, >> but the wiki said it was, so here goes: >> >> I think it would make sense to offer an implementation of Threefish >> (developed in part by Bruce Schneier and Niels Ferguson), since it is a >> reasonably fast block cipher, is tweakable, and is the only serious block >> cipher (that I know of, at least) to offer a very wide variant (1024 bits >> wide). Additionally, it avoids cache-timing attacks by not using S-boxes or >> table lookups (something which I am absolutely sure you address in your >> implementation of AES, but all the same it is nice to know that one is >> using a block cipher developed explicitly to avoid such problems). >> >> Better still, the C reference implementation of Threefish provided by >> the group that developed it is uncopyrighted, so it should be able to be >> included in this project with minimal effort. >> >> Anyway, this is just a suggestion I thought I would bring up, since it >> would be nice to have more ciphers to choose from, and the reasons given >> above for including this particular cipher. >> >> -- Collin >> >> -- >> -- >> You received this message because you are subscribed to the "Crypto++ >> Users" Google Group. >> To unsubscribe, send an email to [email protected] >> <javascript:>. >> More information about Crypto++ and this group is available at >> http://www.cryptopp.com. >> --- >> You received this message because you are subscribed to the Google Groups >> "Crypto++ Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> > -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
