[ 
https://issues.apache.org/jira/browse/CAMEL-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang resolved CAMEL-6875.
---------------------------------

    Resolution: Fixed

Applied the patch into trunk and camel-2.12.x branches.

> PGP Data Format: Allow keyring with several secrete keys, keys with several 
> UserIds, select keys in unmarschalling by keyId
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6875
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6875
>             Project: Camel
>          Issue Type: Improvement
>          Components:  camel-crypto
>            Reporter: Franz Forsthofer
>            Assignee: Willem Jiang
>             Fix For: 2.12.2, 2.13.0
>
>         Attachments: 0001-pgp-data-format-improvements.patch, pubring.gpg, 
> secring.gpg
>
>
> I made several improvements.
> * marschal
> ** signature private key is looked up by user ID --> secrete keyring can now 
> contain several secret keys
> ** improvment in lookup of encryption public key: take into account that a 
> key can have several user IDs
> * unmarshal
> ** take into account that symmetric key can be encrypte by several public 
> receiver keys --> search for the relevant encryption package for which a 
> public key in the keyring exists (part of the code did already exist but not 
> consistently)
> ** take into account that you do not know in advance which of the private 
> keys  in the keyring you must use to verify the signature --> determine the 
> private key from the key Id given in the signature package
> *** a consequence of this is that you do not know which passphrase you must 
> provide for the private key. Therefore a passphrase accessor was introduced.
> I also updated the test resources pubring.gpg and secring.gpg;
> I attached them also in case they cannot be imported via the patch.
> I can do the update of the wiki page.
>  



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to