Hal wrote: > The AES process required all entrants to submit a Java implementation > coded to a specified API. If we made our crypto interface call the crypto > code using that API, we could plug in any one of the AES candidates > (including the eventual winner) without changing a line of code, just > changing which module we link with.
Yup, one of the benefits you get from using an AES candidate is that the reference implementations are all speced to use the same API. If you use any of the AES candidates for the time-being you can just swap the module from underneath the Freenet code once the AES is chosen. Very future proof, indeed. The optimized AES Java reference implementations can be found at http://csrc.nist.gov/encryption/aes/round2/r2algs-code.html Either of the 5 remaining AES candidates will work just fine for now. You wouldn't incur much of a risk even if you were to roll dice as to which AES candidate to pick to cover the 6 months tops it will take before AES is announced. Or pick your personal favorite to show support. If that happens to be Twofish, go for it. --Lucky Green <shamrock at cypherpunks.to> "Among the many misdeeds of British rule in India, history will look upon the Act depriving a whole nation of arms as the blackest." - Mohandas K. Gandhi, An Autobiography, pg 446 http://www.citizensofamerica.org/missing.ram _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
