geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <>
Subject [jira] Commented: (GERONIMO-880) Geronimo ships patent-protected bouncycastle IDEA implementation.
Date Thu, 18 Aug 2005 11:03:56 GMT
    [ ] 

Rick McGuire commented on GERONIMO-880:

Hmmm, another problem here.  The provider jar file is signed (a requirement for hooking in
the JCE), which means we're unable to disable the idea code ourselves.  I posted a question
about this on the bouncycastle dev list, and they might be willing to build us a jar file
without the IDEA code included. 

> Geronimo ships patent-protected bouncycastle IDEA implementation.
> -----------------------------------------------------------------
>          Key: GERONIMO-880
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: OpenEJB, console
>  Environment: All
>     Reporter: Rick McGuire
>  Attachments:
> Current Geronimo is shipping the full bouncycastle jar file, which includes an implementation
of the IDEA encryption algorithm.  Additionally, the openejb code explicitly includes the
IDEA algorithm in its supported cryptography suite.
> The IDEA algorithm is a bit problematic, since the royalty agreement is for non-commercial
use only...royalties are expected for commercial use.  It's not clear what the definition
of commercial use would actually be, but any user building a commercial website with Geronimo
might be at risk for a patent claim just from the presence of the code.  Additionally, since
there is no way to explicitly enable or discable the IDEA suite, a user might be using the
code for commercial purposes without even knowing it. 
> The presence of this code is also a problem for any companies wishing to embed Geronimo
in a commercial offering.  Having this code in the Geronomo base would probably kick in the
commercial uses clause and make those companies subject to royalties.
> The IDEA code code in bouncycastle is not easily removed because the encryption engines
are not dyamically loaded.  It would be a simple matter to replace the IDEA engine class with
a simple one that merely threw an exception (see attached class).  The openejb code probably
needs to remove the IDEA algorithms from the supported list as well. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message