You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/10/21 19:53:34 UTC

[jira] [Commented] (CAMEL-7938) Crypto won't decrypt message with multiple encrypted parts if "our" key isn't the first part

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

ASF GitHub Bot commented on CAMEL-7938:
---------------------------------------

GitHub user steveardis opened a pull request:

    https://github.com/apache/camel/pull/305

    CAMEL-7938 - Crypto won't decrypt message with multiple encrypted parts if "our" key isn't the first part

    CAMEL-7938 patch.  Note that this patch was made off the last commit in 2.11.x, based on when I actually made the fix.  I'd like to see this fix move into the next possible release, so I wasn't sure which commit to actually make it against.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/steveardis/camel crypto_multiple_encrypted_parts

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/305.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #305
    
----
commit 041b4591f41bef5bed9c3ff32f09973230aee5a3
Author: Steve Ardis <st...@cypresscare.com>
Date:   2013-08-19T19:19:09Z

    CAMEL-7938 - Fixed issue with camel-crypto not iterating through encrypted parts and finding the one that goes with our private key; for example - if the payload was encrypted for recipients A and B (in that order), and "our key" is B, the private key lookup fails

commit fa4b061d23dd470abcfa8849be97ba32271c4c99
Author: Steve Ardis <st...@cypresscare.com>
Date:   2014-10-21T17:46:33Z

    CAMEL-7938 - Removed changes to pom.xml

----


> Crypto won't decrypt message with multiple encrypted parts if "our" key isn't the first part
> --------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7938
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7938
>             Project: Camel
>          Issue Type: Bug
>          Components:  camel-crypto
>    Affects Versions: 2.11.1
>            Reporter: Steve Ardis
>
> If a message has multiple PGPPublicKeyEncryptedData (meaning, multiple recipients), PGPDataFormat fails to decrypt the message (unless our key is the first PGPPublicKeyEncryptedData element).
> Said differently, if a message is encrypted for recipient A and B (and the encrypted parts are in that order) and we are recipient B, the message fails to decrypt.
> This definitely affected version 2.11.1.  Looking at the latest version of the same files, this is most likely still an issue.  The fix in the patch that will be supplied is currently being used in our application, but unfortunately I do not have a test case available.
> I will create a pull-request on Github shortly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)