This sounds ok to me.

Regarding the JCEs, I vaguely recollect someone on the list claiming
they made it work with whatever JCE providers
come with WebSphere but I might be mistaken.  

Best Regards,
George

-----Original Message-----
From: Fred Dushin [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, April 22, 2008 12:17 PM
To: George Stanchev
Cc: wss4j-dev
Subject: Re: IDEA patents and BouncyCastle

I was thinking along the lines of a little pluggable piece of code,
which would let the user initialize the JCE, as needed.  This code could
be dynamically loaded, and driven off configuration and findable on the
CLASSPATH (to hopefully mitigate race conditions with our
startup/initialization code).

To get to your immediate question, the only JCE providers I've worked
with with WSS4J is BC, so I'm not sure I'd be of much help in putting
together such a list.

-Fred

On Apr 22, 2008, at 2:09 PM, George Stanchev wrote:

> That's excactly the reason Eclipse legal stays away from BC.
>
> If we can get away from hardcoded dependency from BC JCE, it'd be 
> awsome!
>
> May be we can produce a list of compatible JCEs that can be used with 
> WSS4J (including BC).
>
> Best Regards,
> George
>
> -----Original Message-----
> From: Fred Dushin [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 22, 2008 11:19 AM
> To: wss4j-dev
> Subject: IDEA patents and BouncyCastle
>
> Has the WSS4J team digested this discussion on apache-legal? [1]  See 
> the thread 'IDEA block cipher inclusion via the "bouncy castle" JCE
> provider':
>
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200508.mbox
> /d
> ate?1
>
> I propose we remove the BouncyCastle JARs from our "other"
> distribution, and add a note in the release notes, saying that users 
> must procure a copy of the BC jars themselves.
>
> -Fred
>
> [1] Thanks to Dan Kulp for pointing this out
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they 
> are addressed. Any unauthorized review, use, disclosure or 
> distribution is prohibited. If you are not the intended recipient, 
> please contact the sender by reply e-mail and destroy all copies of 
> the original message.
> **********************************************************************
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to