Re: gpg/pgp noise
On Tue, May 08, 2012 at 02:29:39PM +0300, Mika Suomalainen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 08.05.2012 14:20, Lisi kirjoitti:
> > On Tuesday 08 May 2012 12:11:56 Indulekha wrote:
> >> On Tue, May 08, 2012 at 11:53:23AM +0100, Phil Dobbin wrote:
> > Increasing the pool of servers that gpg checks may alleviate your
> > problem but it's more than likely to be people haven't exported
> > their key.
> >
> > Mine has been exported. See how you view that one.
> >
> > Cheers,
> >>>
> >>> Thanks, Phil. After adding the keyserver Mika suggested, I no
> >>> longer see the error messages but do still have to see this
> >>> messy block of text
> >>>
> >>> at the end:
> >
> > But did you after Phil's?
> >
> > Lisi
> >
> >
>
> That signature block informs to be bad signature from Phil.
>
> > Viestin sisennettyä osaa (vastausta) on luultavasti muokattu
> (In English: The indented part of message (reply) has been possibly
> changed)
> > gpg -komento ja -tuloste:
> In English: gpg -command and -output:
> > /usr/bin/gpg2 gpg: Signature made ti 8. toukokuuta 2012 13.53.22
> > EEST using RSA
> key ID A093C263
> > gpg: BAD signature from "Phil Dobbin <bukowskiscat@gmail.com>"
>
> - --
> Mika Suomalainen
> gpg --keyserver pool.sks-keyservers.net --recv-keys 4DB53CFE82A46728
> Key fingerprint = 24BC 1573 B8EE D666 D10A AA65 4DB5 3CFE 82A4 6728
> http://mkaysi.github.com/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQIcBAEBAgAGBQJPqQOhAAoJEE21PP6CpGcoIlAP/jo6enkTnXc0Ko9pvtJ8Xx5T
> 3lipNMEO0IEf1CN0Yz7392rr/8hvzSTCrBZPXQOyWs7D5EDTlTFsyq9c25MTv1vg
> mGyu0MECbhDuBBG+1XbZpSGIJpHW2GWCcepr55IR7efA3kDhRfYUbbFoey9Uq85g
> Co78ZzfebVvDchcDs/gFnIrq093YTfKgc9sJTJFFmejNjOZMty8XYVjvkDaYA+Kv
> FhFqKO/EsAtUxotHMR2ZhFQrBBXJELIgoDOhgMK/zoSfsXsY2gTgCGxhSf8fRC3g
> 1bpX7qAJ3c0+VcQzWm1GnWKIgPZJgLHmmhPBryszB+fZQuJ4E6arSfvOY/Kiryrr
> 30rrbqmGFBfEiDziZ4aDEvE3ArajsmW10HZv5VfdBV7dWVgxZgm0+JP6Q3NsvZpp
> AfMeV/fUl8dzyXzlZ0ddFkdBl09VCWw2/oCAwLzutfEoUSA0sXLh2njd17gTrOBc
> 7Z23l78fuTOR1BxXp9/8lJwzOydv9QRd66/jUAZ74lSrIKDslsWsgvkQx0PK0u78
> lp2xFJVtMQpcrllmxbo3DbB/QAGkYPppl+706sAeOl9FtWXpbdwoc6fx5hB2DRQ+
> Sos35nWjSSkuIJdRd1KkWAr0miNXUxUQ8n5avgKmbmaypIENGMcVRVKH30dNMrBN
> 7eqBx4ci5qNUlUBRGpQl
> =QAdu
> -----END PGP SIGNATURE-----
>
>
Yes, yours also still shows the (useless) text block at the end.
Jochem Spieker setup is correct, and the block is gone using the
recipe he provided.
A few years ago I went through all this for the exact same reasons,
and ISTR at least half of all pgp/gpg signed mail I received was
done incorrectly.... I just hate that.
--
❤ ♫ ❤ ♫ ❤ ♫ ❤
Indulekha
Reply to: