Scott, Juice uses openSSL as its engine, this provides a 3-6 time improvement when compared to BouncyCastle. As for the deployers: I just sent an e-mail to the list that asks for Juice being FIPS certified :-). openSSL is FIPS certified, Juice is a JCE compliant front-end to openSSL thus quite some people seem to like Juice also beeing FIPS certified.
OpenSSL may use HW acceleration if configured and setup for this, thus with Juice you immediatly have this benefit as well. Regards, Werner Scott Cantor wrote: >> If we want to keep this going - we need to call it out now. > > Just for the record, there was never all that much interest from the > original source of the code (Internet2) in maintaining it. We found it > unnecessary after Raul sped up the Java library several years back, and > combining Java with native code for this kind of thing is just unwieldy for > deployers. > > My experience is that the speed up just isn't large enough, and if it's > worth the hassle to get native code to work, using hardware acceleration > directly is probably more useful. > > -- Scott > > >
