camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Resolved] (CAMEL-6837) PGP Data Format:allow other JCE providers than BC
Date Fri, 11 Oct 2013 13:24:42 GMT


Claus Ibsen resolved CAMEL-6837.

       Resolution: Fixed
    Fix Version/s:     (was: 2.11.3)

Thanks for the patch.

The init of the provider should not be done from marshal/unmarshal as you can have concurrency
issues or whatnot.

So I extended ServiceSupport and added the init logic to doStart/doStop which is the correct

Also added the provider option to the model in camel-core so people can configure it in xml
/ dsl

> PGP Data Format:allow other JCE providers than BC
> -------------------------------------------------
>                 Key: CAMEL-6837
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components:  camel-crypto
>            Reporter: Franz Forsthofer
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.12.2, 2.13.0
>         Attachments: 0001-pgp-jce-provider-parameter-added.patch
> PGP Data Format is currently using the Bouncy Castle JCE provider. The attached patch
opens the PGP Data Format for other JCE providers. 
> I made tests with the IAIK JCE Provider and it was working fine. Unfortunately, the SunJCE
provider cannot be used because it does not contain the message digest algorithms (the message
digest algorithm are contained in the other provider with name 'SUN') and the PGP bouncy caslte
API only allows specifying one provider.

This message was sent by Atlassian JIRA

View raw message