Thus spake Richard Levitte - VMS Whacker: > From: Stephen Sprunk <[EMAIL PROTECTED]> > > stephen> After implementing CBC, CFB, OFB, and CTR for AES (mostly plagiarized > stephen> from IDEA), I'm beginning to wonder why we have 40 different > stephen> implementations of the exact same algorithms in the first place. > stephen> Couldn't we have a general "modes" macro set, to which you pass the > stephen> ECB function of the cipher you're using? > > The current state is EAY legacy. His idea was that one should be able > to pick out any of the algorithm directories and create a separate > library for them (the old libdes is actually exactly the same as > crypto/des/).
First of all, do we still think that's necessary, given the wide acceptance of OpenSSL and libcrypto? In either case, it shouldn't be that difficult to develop a macro set that implements various modes. Pass in some function names, block size, types for casts, and let it generate the boilerplate. Worth doing? S -- Stephen Sprunk "So long as they don't get violent, I want to CCIE #3723 let everyone say what they wish, for I myself have K5SSS always said exactly what pleased me." --Albert Einstein ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
