You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Franz Forsthofer (JIRA)" <ji...@apache.org> on 2014/02/11 13:08:20 UTC

[jira] [Updated] (CAMEL-7192) PGPDataFormat: Sub-Key not supported for signing and correct selection of encryption/signing key via KeyFlag

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

Franz Forsthofer updated CAMEL-7192:
------------------------------------

    Attachment: 0001-use-key-flags-for-determining-encryption-signing-key.patch

> PGPDataFormat: Sub-Key not supported for signing and correct selection of encryption/signing key via KeyFlag
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7192
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7192
>             Project: Camel
>          Issue Type: Bug
>          Components:  camel-crypto
>    Affects Versions: 2.12.2
>            Reporter: Franz Forsthofer
>             Fix For: 2.12.3, 2.13.0
>
>         Attachments: 0001-use-key-flags-for-determining-encryption-signing-key.patch
>
>
> A PGP key ring with version 4 keys typically consists of a primary key which has sub-keys. There is a use-case where the primary key has only the usage flag (KeyFlag) "certify" and one sub-key is makred with the usage flag "signing" and the other sub-key is marked with usage flag"encryption".  In this case the PGPDataFormat does not use the correct sub-key for signing and encryption.
> In the patch I enabled the usage of sub-keys for the signing process and I introduced the usage flag (KeyFlag) for finding the correct keys for signing and encryption.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)