You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Samuel Meder <me...@mcs.anl.gov> on 2004/07/16 16:45:50 UTC

WSS4J and custom ciphers

We've been looking at converting our existing code to use WSS4J and have
come upon the following stumbling block wrt to encryption:

To work out the encryption using gss_wrap/unwrap we decided that it was
best to encapsulate these calls in a JCE Cipher provider. We're now
looking at some (hopefully) minor problems that this is causing:

      * WSSecurityUtil.prepareSecretKey() has a limited set of algorithm
        URI to JCE provider id mappings. It would be great if we could
        add a generic clause that would use the xmlsec algo URI to
        provider id mapping file (or even make the whole thing generic,
        I think the 3DES bit can be replaced with "SecretKeySpec keySpec
        = new SecretKeySpec(rawKey, "DESede");"). Would you accept a
        patch for this?
      * (minor unrelated nit) WSSecurityUtil.getCiperInstance() should
        probably be WSSecurityUtil.getCipherInstance()
/Sam
-- 
Sam Meder <me...@mcs.anl.gov>
The Globus Alliance - University of Chicago
630-252-1752



Re: WSS4J and custom ciphers

Posted by Davanum Srinivas <da...@gmail.com>.
+1 to both. Please submit a patch in JIRA (http://issues.apache.org/jira/)

thanks,
dims

On Fri, 16 Jul 2004 09:45:50 -0500, Samuel Meder <me...@mcs.anl.gov> wrote:
> 
> We've been looking at converting our existing code to use WSS4J and have
> come upon the following stumbling block wrt to encryption:
> 
> To work out the encryption using gss_wrap/unwrap we decided that it was
> best to encapsulate these calls in a JCE Cipher provider. We're now
> looking at some (hopefully) minor problems that this is causing:
> 
>       * WSSecurityUtil.prepareSecretKey() has a limited set of algorithm
>         URI to JCE provider id mappings. It would be great if we could
>         add a generic clause that would use the xmlsec algo URI to
>         provider id mapping file (or even make the whole thing generic,
>         I think the 3DES bit can be replaced with "SecretKeySpec keySpec
>         = new SecretKeySpec(rawKey, "DESede");"). Would you accept a
>         patch for this?
>       * (minor unrelated nit) WSSecurityUtil.getCiperInstance() should
>         probably be WSSecurityUtil.getCipherInstance()
> /Sam
> --
> Sam Meder <me...@mcs.anl.gov>
> The Globus Alliance - University of Chicago
> 630-252-1752
> 
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/

Re: WSS4J and custom ciphers

Posted by Werner Dittmann <We...@t-online.de>.
+1 from me too. In particular to the getCiperInstance()  fix :-).

Regards,
Werner


----- Original Message -----
From: "Samuel Meder" <me...@mcs.anl.gov>
To: "fx-dev" <fx...@ws.apache.org>
Cc: "Thomas Sandholm" <sa...@pdc.kth.se>; "Jarek Gawor"
<ga...@mcs.anl.gov>; "Rachana Ananthakrishnan" <ra...@mcs.anl.gov>
Sent: Friday, July 16, 2004 4:45 PM
Subject: WSS4J and custom ciphers


>
> We've been looking at converting our existing code to use WSS4J and have
> come upon the following stumbling block wrt to encryption:
>
> To work out the encryption using gss_wrap/unwrap we decided that it was
> best to encapsulate these calls in a JCE Cipher provider. We're now
> looking at some (hopefully) minor problems that this is causing:
>
>       * WSSecurityUtil.prepareSecretKey() has a limited set of algorithm
>         URI to JCE provider id mappings. It would be great if we could
>         add a generic clause that would use the xmlsec algo URI to
>         provider id mapping file (or even make the whole thing generic,
>         I think the 3DES bit can be replaced with "SecretKeySpec keySpec
>         = new SecretKeySpec(rawKey, "DESede");"). Would you accept a
>         patch for this?
>       * (minor unrelated nit) WSSecurityUtil.getCiperInstance() should
>         probably be WSSecurityUtil.getCipherInstance()
> /Sam
> --
> Sam Meder <me...@mcs.anl.gov>
> The Globus Alliance - University of Chicago
> 630-252-1752
>
>


Re: [VOTE] Sam Meder as WS-FX Committer

Posted by ja...@opensource.lk.
+1 From me..

Jaliya

> Folks,
>
> Sam will be ramping up his work on WSS4J soon...(Sam, It was great
> meeting you in Sri Lanka) So let's VOTE to grant him commit privs for
> all WS-FX projects.
>
> Here's mine: +1 to grant Sam commit privs for ws-fx.
>
> thanks,
> dims
>
> On Fri, 16 Jul 2004 09:45:50 -0500, Samuel Meder <me...@mcs.anl.gov>
> wrote:
>>
>> We've been looking at converting our existing code to use WSS4J and have
>> come upon the following stumbling block wrt to encryption:
>>
>> To work out the encryption using gss_wrap/unwrap we decided that it was
>> best to encapsulate these calls in a JCE Cipher provider. We're now
>> looking at some (hopefully) minor problems that this is causing:
>>
>>       * WSSecurityUtil.prepareSecretKey() has a limited set of algorithm
>>         URI to JCE provider id mappings. It would be great if we could
>>         add a generic clause that would use the xmlsec algo URI to
>>         provider id mapping file (or even make the whole thing generic,
>>         I think the 3DES bit can be replaced with "SecretKeySpec keySpec
>>         = new SecretKeySpec(rawKey, "DESede");"). Would you accept a
>>         patch for this?
>>       * (minor unrelated nit) WSSecurityUtil.getCiperInstance() should
>>         probably be WSSecurityUtil.getCipherInstance()
>> /Sam
>> --
>> Sam Meder <me...@mcs.anl.gov>
>> The Globus Alliance - University of Chicago
>> 630-252-1752
>>
>>
>
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
>


Re: [VOTE] Sam Meder as WS-FX Committer

Posted by Dimuthu Leelarathne <mu...@opensource.lk>.
Hi,

Here is my vote: +1

Yes. It was nice meeting you in Sri Lanka.

Regards,
Dimuthu.
-- 
Lanka Software Foundation  http://www.opensource.lk

> Folks,
>
> Sam will be ramping up his work on WSS4J soon...(Sam, It was great
> meeting you in Sri Lanka) So let's VOTE to grant him commit privs for
> all WS-FX projects.
>
> Here's mine: +1 to grant Sam commit privs for ws-fx.
>
> thanks,
> dims
>
> On Fri, 16 Jul 2004 09:45:50 -0500, Samuel Meder <me...@mcs.anl.gov>
> wrote:
>>
>> We've been looking at converting our existing code to use WSS4J and have
>> come upon the following stumbling block wrt to encryption:
>>
>> To work out the encryption using gss_wrap/unwrap we decided that it was
>> best to encapsulate these calls in a JCE Cipher provider. We're now
>> looking at some (hopefully) minor problems that this is causing:
>>
>>       * WSSecurityUtil.prepareSecretKey() has a limited set of algorithm
>>         URI to JCE provider id mappings. It would be great if we could
>>         add a generic clause that would use the xmlsec algo URI to
>>         provider id mapping file (or even make the whole thing generic,
>>         I think the 3DES bit can be replaced with "SecretKeySpec keySpec
>>         = new SecretKeySpec(rawKey, "DESede");"). Would you accept a
>>         patch for this?
>>       * (minor unrelated nit) WSSecurityUtil.getCiperInstance() should
>>         probably be WSSecurityUtil.getCipherInstance()
>> /Sam
>> --
>> Sam Meder <me...@mcs.anl.gov>
>> The Globus Alliance - University of Chicago
>> 630-252-1752
>>
>>
>
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
>


[VOTE] Sam Meder as WS-FX Committer

Posted by Davanum Srinivas <da...@gmail.com>.
Folks,

Sam will be ramping up his work on WSS4J soon...(Sam, It was great
meeting you in Sri Lanka) So let's VOTE to grant him commit privs for
all WS-FX projects.

Here's mine: +1 to grant Sam commit privs for ws-fx.

thanks,
dims

On Fri, 16 Jul 2004 09:45:50 -0500, Samuel Meder <me...@mcs.anl.gov> wrote:
> 
> We've been looking at converting our existing code to use WSS4J and have
> come upon the following stumbling block wrt to encryption:
> 
> To work out the encryption using gss_wrap/unwrap we decided that it was
> best to encapsulate these calls in a JCE Cipher provider. We're now
> looking at some (hopefully) minor problems that this is causing:
> 
>       * WSSecurityUtil.prepareSecretKey() has a limited set of algorithm
>         URI to JCE provider id mappings. It would be great if we could
>         add a generic clause that would use the xmlsec algo URI to
>         provider id mapping file (or even make the whole thing generic,
>         I think the 3DES bit can be replaced with "SecretKeySpec keySpec
>         = new SecretKeySpec(rawKey, "DESede");"). Would you accept a
>         patch for this?
>       * (minor unrelated nit) WSSecurityUtil.getCiperInstance() should
>         probably be WSSecurityUtil.getCipherInstance()
> /Sam
> --
> Sam Meder <me...@mcs.anl.gov>
> The Globus Alliance - University of Chicago
> 630-252-1752
> 
> 


-- 
Davanum Srinivas - http://webservices.apache.org/~dims/