[ 
https://issues.apache.org/activemq/browse/CAMEL-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58108#action_58108
 ] 

Stephen Gargan commented on CAMEL-2527:
---------------------------------------

I'd a feeling that wasn't going to fly but I didn't want to add a dependency 
(e.g. commons-codec) particularly as this is in core. Its annoying that the JDK 
doesn't include standard Base64 utilities but Camel might benefit from its own. 
The question remains though should I Roll my own or fork one.

I'd much rather not re invent the wheel, as It would be difficult to make it 
any rounder than either of these :)

- http://iharder.sourceforge.net/current/java/base64/ (Public Domain)
- 
http://svn.apache.org/repos/asf/commons/proper/codec/trunk/src/java/org/apache/commons/codec/binary/
 (Apache2)

This is not my call though. What do you prefer?

I'll make the other changes and resubmit a patch. 


> Addition of DSL to sign and verify exchanges with Digital signatures.
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-2527
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2527
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core, camel-spring
>            Reporter: Stephen Gargan
>            Priority: Minor
>             Fix For: 2.3.0
>
>         Attachments: signature-core.patch, signature-spring.patch, 
> signature-wiki.txt
>
>
> I've put together and extension to the DSL that will enrich exchanges with a 
> Digital Signature cacluated using the payload. The signature is stored in a 
> property of the exchange and can be used to verify it at a later stage. It 
> uses the JCE under the covers and It adds the constructs 'sign' and 'verify' 
> to the dsl. Basically it will allows you to do the following
> from("direct:sign").sign(somePrivateKey).to("direct:signaturetest");
> and later 
> from("direct:signaturetest").verify(somePublicKey).to(...);
> Keys can be supplied from keystores or in message headers for dynamic 
> signing, the attached wiki page explains the feature set in more detail. 
> The patch contains a binary keystore so to apply it you should run 
> patch -p0 --binary -i signature-core.patch
> Give it a try and see what you think. I'm also in the processor finishing up 
> a CryptoDataFormat that uses the JCE to encrypt and decrypt exchange 
> payloads, its about 90% done and I should get it out soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to