Daniel Pocock created CAMEL-8403:
------------------------------------

             Summary: support for PGP clear-signed (ASCII-armored signature 
without encryption)
                 Key: CAMEL-8403
                 URL: https://issues.apache.org/jira/browse/CAMEL-8403
             Project: Camel
          Issue Type: New Feature
          Components:  camel-crypto
    Affects Versions: 2.14.1
         Environment: n/a
            Reporter: Daniel Pocock


It is quite common to send emails that have a signature but no encryption.

A typical example of such an email is a release announcement from a free 
software project.

The marshalled message body should be human-readable but will either:
a) have an ASCII armored signature at the bottom
b) have a signature in a MIME attachment

Maybe the PGP marshaller should just put the binary version of the PGP 
signature in a header and then other data formats can be used for either the 
ASCII-armoring or conversion to MIME?

However, if the message body is already MIME (possibly with attachments), then 
the PGP data format may need to be able to sign each attachment and then the 
marshalled data will also be a MIME message but with additional signature 
attachments.

Below is an example of the most simple case, clearsigning "Hello world" with 
the gpg command.  The PGP data format should be able to both marshal the body 
"Hello world" into a message like that below and also unmarshal/verify it.

When unmarshalling the message below, the signature stuff should all be removed 
and the body will just become "Hello world" again.

$ echo "Hello world" | gpg --clearsign
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello world
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJU7ZjuAAoJEOm1uwJp1aqDcqwQAKVl4YQyL9VG+Vwy7y5W5Frb
mlhqibqquaYFc6HQvw+RLy9zicowdoMiXK4NRPxzTm5+PFxHXjgVMSFSDWNvuO6E
fzzkGOnyZdzPbFq+d0q1uMs4EnqfqHX/Y8v6PyWPdyHD8Isu7if0xpGNXbWGZMQn
jNGQzvj2t1lYqDP9DJDnctROI5qVDzXqR69pmgG+J9ZzaZW4EJmkitt9BJIath0a
ueVc5XJroGGj7KBJSyQAbpEhEO6b9Kz4cXCUqUfHTdKgVjO9UBfAZpmCappwMbDH
yvaAvUq1lAIncIS5ocWVvz66qG/tver5jrruGU5ptEwn9At/ZyKp88nvM09hNzuN
4Q6dFcytKtnEc2mSDeQ3/IFgT0FVU9vFhP8UusdfHF5GOBfsTWLc0RJdofCo27JN
jy1fHj9LroM7m0S/3ln7yQaa9qzatCOctzqq4d0xo8zX5WZ/7Eo9gwYgNUKg0WsU
PgZrzov0ImeULJvj43i2IMfojQSAN7aXnVPW817stIoKmkZpavH4TutfV6DDgbGa
UfsiYQ3BX/o/cfPB88SWmEMWZvP7syDwxK+iBzPDtwAexIAYP9NURfyWZvWe1ZBl
zdR/6pN8VR6/R17jJr3YCjpFlDs4zG67QoI8qSl91TH2h4V7uPQbaOUaSdAoh9Z6
TXpyXYPk5GTGx8rf5v5E
=Qbwp
-----END PGP SIGNATURE-----




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

Reply via email to