camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan McGuire (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5475) Can't unmarshal pgp messages encrypted with ElGamal.
Date Wed, 01 Aug 2012 04:59:34 GMT


Bryan McGuire commented on CAMEL-5475:

The RSA keys used for the existing tests just need to be swapped out for ElGamal keys.

delete pubring.gpg and secring.gpg from  components/camel-crypto/src/test/resources/org/apache/camel/component/crypto/

Then with gnupg, regenerate the rings as ElGamal:
gpg --homedir components/camel-crypto/src/test/resources/org/apache/camel/component/crypto/

it will ask questions as gpg is an interactive program:
For type of key
Pick DSA/ElGamal
For bit length, 1024 is fine
Pick 0 to make the key never expire
confirm yes if asked
For Real Name, use "Super"
For email, use ""
For passphrase, use "sdude"
Confirm with O for Okay

run the unit test and watch for some failures.
apply the patches I submitted to PGPDataFormat and PGPDataFormatUtil and watch all tests pass.

svn revert the keys, and watch it pass again with the old keys.
> Can't unmarshal pgp messages encrypted with ElGamal.
> ----------------------------------------------------
>                 Key: CAMEL-5475
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components:  camel-crypto
>    Affects Versions: 2.10.0, 2.11.0, Future
>         Environment: All environments
>            Reporter: Bryan McGuire
>            Assignee: Willem Jiang
>         Attachments: patch.txt
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> Current strategy for finding the private key is to iterate the secret keychain and matching
on the configured email address.  This is incorrect; the secret key chain should be searched
by the key id found in the public key encrypted message. What happens now is the DSA signing
key is matched instead of the ElGamal decryption key, and this throws

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message