Stop-gap for signature flooded keys

[Werner Koch]

Hi!

In case the problem with too many key signatures accidently retrieved
from a keyserver or from elsewhere turns more virolent, the two attached
patches might help.  They should apply to 2.2.16 and allow to put

--8<---------------cut here---------------start------------->8---
keyserver-options self-sigs-only 
--8<---------------cut here---------------end--------------->8---

into gpg.conf to skip all key-signatures at an early import stage.  This
will go into 2.2.17.  We track this problem at https://dev.gnupg.org/T4591


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-gpg-Make-read_block-in-import.c-more-flexible.patch
Type: text/x-diff
Size: 2825 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20190701/c02b0930/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-gpg-New-import-and-keyserver-option-self-sigs-only.patch
Type: text/x-diff
Size: 5143 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20190701/c02b0930/attachment-0001.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20190701/c02b0930/attachment.sig>