The other place BountyCastle may be relevant is in invoker encryption as part of the remoting project.
Jason T. Greene wrote: > We need it to support WS-Security on jdk 4. Since, at the time of > releasing jbossws 1.0.0, we did not have a US export license, we > currently rely on the user to download and install it in their JVM. > > -Jason > > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:jboss- >> [EMAIL PROTECTED] On Behalf Of Scott M Stark >> Sent: Tuesday, June 20, 2006 11:31 AM >> To: jboss-development >> Subject: [JBoss-dev] BouncyCastle IDEA issues >> >> A concern over use of BouncyCastle as a JCE provider has come up due >> > to > >> its inclusion of the IDEA algorithm implementation that is subject to >> patent/ip concerns. As far as I know we don't have any explicit or >> implicit dependency on BouncyCastle even though it has been discussed >> > in > >> the context of WS-Security. If we actually are moving to requiring >> BouncyCastle I need to know why. >> >> xxxxxxxxxxxxxxxxxxxxxxxxxxxx >> Scott Stark >> VP Architecture & Technology >> JBoss, a division of Red Hat >> xxxxxxxxxxxxxxxxxxxxxxxxxxxx >> >> >> >> _______________________________________________ >> JBoss-Development mailing list >> JBoss-Development@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > > _______________________________________________ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
