Jean-Pierre, Thank you for your efforts!
Re. Mac OS X patches - they don’t introduce any incompatibility, especially because most of them are contained in the GNUmakefile, and are isolated by “ifeq … endif”. Re. Post-Quantum - I think McEliece would work just fine, especially if the “no key minimization” approach is taken (as mentioned in the Wiki I referred to)... Thanks! On Dec 28, 2014, at 6:29 , Jean-Pierre Münch <[email protected]> wrote: > Hey guys, > > thank you for your responses. > I will now tell you my evaluation: > > NTRU: I looked it up and actually found an open-source implementation. But > the problem with it though is that the guys providing the implementation (I > believe they are the inventors) want money for commercial applications. > Crypto++ is a library where every single source file is placed in the public > domain and the whole library is under boost-license. I don't think we can > incorporate NTRU. But once I finished all the stuff (which may take me some > months) i'll contact Wei Dai and ask wether NTRU is possible. > > BUT: If everything you wan't is Post-Quantum PK-encryption i'll see what's > possible concerning McEliece. > > Blake: It got the same problems as Skein does: it's multiple files > large.>From a license point of view BLAKE won't pose any problems and I think > I'll incorporate it right after skein. > > Inclusion of FHMQV shouldn't pose any problems and will be done. > > OS X patches will be included if and only if they don't produce > incompabilities with other platforms (linux & windows). I'll test windows and > once finished I'll post the whole library in the wiki (and here) and someone > needs to confirm me that compilation works under linux. > > Rijndael is something I proposed myself in a paper (at school) I wrote once. > The problem with Rijndael though is that i'm not sure wether this is > possible. I'll dig more into the implementation of Rijndael and compare with > specifications (I got them somewhere) and see what's possible. The Problem > might still remain that I don't know (yet) how to code using assembler > language and crypto++ got it's own "derivat" of ASM. Conclusion: I can't > promise anything but if (for me) possible I'll do it. > > I'm currently at the point were I set everything up (including some tests) > and fixed everything that Visual Studio's static code analysis found. > Next step will be to integrate the finished stuff and set up tests (with test > vectors) of the stuff I claimed finished. > > If anyone want to participatein this whole modernization process contact me > and we'll find productive ways of cooperation. > > BR > > JPM > > > Am Dienstag, 23. Dezember 2014 15:47:21 UTC+1 schrieb Jean-Pierre Münch: > Hey Guys, > > I'm currently working on something that might interest you: > The modernization of Crypto++ ! > > I'm accumulating source code and sometimes writing some of my own in > preparation of integration into the library. > > The current new things (that have yet been finished) are: > - Threefish, with tweak as part of key > - RSA signature with PKCS#1 v2.0 > - HMAC support for SHA3 and co. > > Yet unfinished modules: > - Threefish as a whole new class of tweakable block ciphers (ay result in > zeroing the tweak for classic ciphers/modes) > - scrypt, there're still some design issues I've to deal with, but this is > rather sooner than later finished. > > Stuff that may cause some problems: > - Skein (as I would like to use the original files, which are unfortunaly > multiple files, need to clarify this at time with WeiDai) > - Fortuna (Submitted the request for allowance of usage at codeproject, after > permission has been granted there's still some work to do to bring this to > Crypto++) > > Post as reply if you think something needs to be added to the list. > > BR > > JPM > > -- > -- > 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. -- -- 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.
