gpg messages error after signing

[Laurent Jumet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Hello dmdm !

dmdm <dmdm00 at yahoo.com> wrote:

> I wonder if I might ask for an example please useing perhaps this line in
> the example

    The answer given to you is exact. Each generation answer adds a "- ", and 
depending what soft you are using, you can go back in generations asking 
several times to Decrypt the same message.
    Each time you ask Decrypt, you go back one generation of keys and 
signatures.
    By this way, you can include a public key in a message and sign the whole. 
First generation of Decrypt/Verify shows you "Good signature from X", second 
generation allows you to include the public key in your keyring and be sure 
it's recommended by the sender.


> -----BEGIN PGP SIGNED MESSAGE-----

> thankyou

> dmdm

> David Shaw wrote:
>>
>> On Mar 7, 2009, at 5:28 AM, dmdm wrote:
>>
>>>
>>> When I sign a message that contains a gpg key what happens is that
>>> the key
>>> has the '-'
>>> missing at top and bottom of key. its ok before its signed .(see
>>> example
>>> below)
>>
>> That is a normal part of OpenPGP called "dash escaping".  Basically,
>> since your signature itself starts with a dash (as part of "-----BEGIN
>> PGP SIGNED MESSAGE-----") any other dashes, such as those surrounding
>> your key that you're including in the signed message, need to be
>> escaped so the message parser does not get confused.  The way this is
>> done is to append a "- " (a dash and a space) to the beginning of each
>> dash.
>>
>> Just verify the message to check the signature, and what comes out of
>> the verification step has all the escaping removed so you can use the
>> key you included.
>>
>> David


- -- 
Laurent Jumet
      KeyID: 0xCFAF704C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iHEEAREDADEFAkmzgb8qGGh0dHA6Ly93d3cucG9pbnRkZWNoYXQubmV0LzB4Q0ZB
RjcwNEMuYXNjAAoJEPUdbaDPr3BMT4AAoLz9lAc5mRaJqnHdJXTtuYPLxdWVAKDS
7GnFl5ntkCTLtZOuLzZdHQEUHg==
=APmB
-----END PGP SIGNATURE-----