On Fri, 2014-06-27 at 13:41 -0400, unixninja92 wrote: > On 06/27/2014 06:31 AM, Steve Dougherty wrote: > >> The next step is to write unit-tests and documentation. I am > >> also planning on submitting a patch for our OCB nonce length > >> problem that will let us upgrade Bouncy Castle to 150, and soon > >> 151 which was just had it's last beta released. I made a copy of > >> the OCB class from BC149 and put it in crypt. I added a boolean > >> to the AEAD classes to decide which version of OCB to use. > > > > While boolean flags do work, I don't think it scales well. Would it > > make sense to have unversioned AEAD classes that give the latest, > > with the option of explicitly requesting a version? Something like > > AEADInputStream vs. AEADInputStream_v149. Older versions could be > > deprecated and removed with time. Maybe an enum instead? > > > I've written a CryptBucket class that can replace the AEADBucket > class, and works directly with AEAD in and out streams. This has an > CryptBucketType enum that tells CryptBucket which version of OCB to > use. Would it make more sense to change the name of the OldOCB class > to OCB_v149? I assume using the oldOCB enum value will be deprecated > and eventually removed.
OCB_v149 is fine Florent
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
