Re: gpg/pgp noise
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
08.05.2012 15:33, Johann Spies kirjoitti:
> On Tue, May 08, 2012 at 01:20:21PM +0200, Jochen Spieker wrote:
>
>>
>> muttrc:
>>
>> set display_filter='sed -f ~/.mutt/display-filter'
>>
>> ~/.mutt/display-filter:
>>
>> /^gpg:/d
>
> Thanks. I have learnt something new in this thread.
>
> I still see similar messages like this on nearly all the signed
> emails in this list:
>
> pg: Signature made Di 08 Mei 2012 13:20:21 SAST using DSA key ID
> D58ADB39 16118146 0|gpg: Can't check signature: public key
> not found
>
> even though I have
>
> keyserver pool.sks-keyservers.net
>
> in my .gnupg/gpg.conf.
>
> Regards Johann
>
Are you receiving the missing keys from keyserver automatically? You
can do this by adding
> keyserver-options auto-key-retrieve
to ~/.gnupg/gpg.conf .
PS. If anyone is interested, my gpg.conf can be found at
https://github.com/Mkaysi/shell-things/blob/master/gnupg/gpg.conf .
- --
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/
iQIcBAEBAgAGBQJPqRaKAAoJEE21PP6CpGcogI0P/1vyrEEXJBXZiZx5SGIfamf7
M14LxqA5p+iQxKni25qnq4Oahrwz78kEerOL01RzXtofFsIqNMHDqxTVakRJHVfk
GiGgis4I0giR9i/skVZCOhj8H3srNJGtRBIUn4ETqhf0YOBtJsYT5Q/lww9jXdnH
5oOoZTcjblsZseVYJPSNDeK5OSznyQGvRSap3s9HuK+vQflz18nXBTUHV7bArSFz
oSlWVrnzKqG5p+cXOhPLE8LWFjZA17qwaDHJ4vXcDGNn3NRRHgWnmTszgYsy5ULT
TW4WDjJHVa2QszBvtwIbogbNsMSPEbpGnqERGXsU8U912bwhsUxf7dg0esenhC8x
RRb0QzfI0w8s+IHs2rrmNc7cAQum3SoMtywqRO68ABzenxVy7qcTGCaQ7q9wWhSU
KoXZlEXBEbOjbm0pnCcR9GWEUPmE1TfN0hv1Ql7KGuozr+rePTPVGDAiK+DpTYEA
1ODbowmLreChZ35oX6oz8cjY/vJjv0yTCAOCLJeyWL9ookvHcLEObVpm8CfbD9gv
YE0vtF8U/Y/Wfy4pYAm1MgffSyKXCOLxIEGXqYT/3nLSv4Whnv9ZOg4obF4NZOI7
W79iRmJ4yr/s99DT4xmgQM0CiYIOpv5WL2fAdlUqJ+nEFb0rxTujZaVh4Jt42WL/
qJs8EU3ddeTpkQO+JAgA
=w2cU
-----END PGP SIGNATURE-----
Reply to: