[Sks-devel] Another Poison Key?

[Simon Lange]

Hi,

i noticed a key, which, whenever one of my peers tries to send it to me, 
is failing and causing unstable enlistment in the sks pool list.

Jan 14 06:48:05 atlas sks[17917]: 2019-01-14 06:48:05 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 08:51:59 atlas sks[17917]: 2019-01-14 08:51:59 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 11:17:11 atlas sks[17917]: 2019-01-14 11:17:11 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 11:38:06 atlas sks[17917]: 2019-01-14 11:38:06 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 12:18:52 atlas sks[17917]: 2019-01-14 12:18:52 Requesting 99 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 13:01:05 atlas sks[17917]: 2019-01-14 13:01:05 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 13:54:08 atlas sks[17917]: 2019-01-14 13:54:08 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 14:12:16 atlas sks[17917]: 2019-01-14 14:12:16 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 14:32:09 atlas sks[10527]: 2019-01-14 14:32:09 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C

As you can see its a still present problem makes it impossible to get 
"these 100 missing keys" from that peer.

The error looks always like that:
Jan 14 15:00:06 atlas sks[10527]: 2019-01-14 15:00:06 111 hashes 
recovered from <ADDR_INET [193.224.163.43]:11371>
Jan 14 15:00:08 atlas sks[10527]: 2019-01-14 15:00:08 Requesting 100 
missing keys from <ADDR_INET [193.224.163.43]:11371>, starting with 
030E4ECA584FC3298423CA5B0CB7855C
Jan 14 15:00:26 atlas sks[10527]: 2019-01-14 15:00:26 100 keys received
Jan 14 15:01:26 atlas sks[10526]: 2019-01-14 15:01:26 add_keys_merge 
failed: Eventloop.SigAlarm
Jan 14 15:01:26 atlas sks[10526]: 2019-01-14 15:01:26 Key addition 
failed: Eventloop.SigAlarm
Jan 14 15:01:26 atlas sks[10526]: 2019-01-14 15:01:26 100 keys found

the only issue in the archive i found so far was this one:
https://lists.nongnu.org/archive/html/sks-devel/2018-11/msg00073.html

...which describes EXACTLY the same symptoms and - maybe - the same 
cause.
So is there any workaround? Does that poisoned key poison the peer 
rendering it as unstable?
Is there some kind of blacklist-workaround or max-key-size setting for 
the sksconf to prevent loading such?

Thanks

Simon

--
PPCIS - Project Leader

signature.asc
Description: OpenPGP digital signature