Please be aware that rebuilding the jar means that it is no longer
signed and does not work as a security provider.
Ff you want to use the bouncycastle security provider and this
recompiled jar in the same application, you will get clashes. Class
Loader fun. The whole monty. :-)
The cleanest solution might be at least change the package names just as
Tomcat does with e.g. DBCP.
best regards
Henning
On Sun, 2007-09-16 at 16:37 +0100, ant elder wrote:
> On 9/16/07, Kevan Miller <[EMAIL PROTECTED]> wrote:
>
> <snip>
>
> I don't see a an unencumbered BouncyCastle distribution which is not
> > encumbered.
>
>
> Is there any reason we can't just make one? The license seems ok for that:
> http://www.bouncycastle.org/licence.html. Is it just the one class in the
> bouncycastle jar that has the IDEA algorithm:
> org.bouncycastle.crypto.engines.IDEAEngine?
>
> If we use some jar processor such as the shade-maven-plugin to strip out
> that one class and create a new bcprov-no-idea-jdk15-136.jar and distribute
> that would that solve this problem? Could even try to get that new jar
> published in a repository somewhere so other projects can use it.
>
> ...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
