key distribution/verification/update mechanisms other than keyservers

[Teemu Likonen]

Werner Koch [2018-01-17 09:58:21+01] wrote:

>>>  (c) rejected all third-party certifications -- so data attached to
>>>  a given primary key is only accepted when certified by that primary
>>>  key.

> This can help to avoid DoS attacks. I would love to see that to get my
> key down to a reasonable size.

Not quite related but... I tend to think that on client side it would be
good idea to "clean" by default. (I like to do that.)

    keyserver-options import-clean,export-clean

-- 
/// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180117/9b6dd5d4/attachment.sig>