removing -----BEGIN PGP SIGNED MESSAGE----
kunalvshah+gnupg at gmail.com
Fri Jul 25 19:08:52 CEST 2008
On Fri, Jul 25, 2008 at 10:33 AM, Kara <karadenizi at earthlink.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> Subject: Re: removing -----BEGIN PGP SIGNED MESSAGE----
> Date: Fri, 25 Jul 2008 02:45:37 -0400
> From: Robert J. Hansen <rjh at sixdemonbag.org>
> To: Kunal Shah <kunalvshah+gnupg at gmail.com>
> CC: GnuPG Users <gnupg-users at gnupg.org>
> Kunal Shah wrote:
>>> Is there any way to avoid that?
> Robert J. Hansen wrote:
>> Sort of. PGP/MIME.
>> If PGP/MIME is not an option for you, then no, there is no way
>> to avoid it. Inline OpenPGP signatures require that text to
>> be present.
> Keep in mind that not all e-mail programs can handle PGP/MIME
> messages. Among them. those provided by Windows which regretfully
> represents an exceptionally high proportion of individuals using
> Although not a GPG/PGP solution, another alternative would be to use
> your computer's S/MIME capability along with x.509 certificates
> (perhaps obtained from either Thawte (www.thawte.com) or CAcert
> (www.cacert.org) or any of the other Certificate authorities that
> offer free x.509 certificates.
> Best wishes for an enjoyable Fri and a great weekend coming up.
In that case, I will need to obtain private key with openssl package
and send my pub key to CA to obtain certificate. However, if i go with
that procedure, my friends who uses GNUPg or PGP will not be able to
verify my signature.
I guess I am running into cross platform issues. in fact, I need to
sign the message using a. GNUPg private key for those who uses GNUPg
and b. S/MIME for those who uses GPG/MIME or S/MIME. is that correct
> Timestamp: Fri 25 Jul 2008, 1033 Local (UTC -0400)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: For keyID and its URL see OpenPGP message header
> -----END PGP SIGNATURE-----
More information about the Gnupg-users