Bug#1002880: signing-party: caff defaults to retired pool.sks-keyservers.net

2021-12-30 Thread Aaron M. Ucko
Guilhem Moulin writes: > Hi, Hi. Thanks for the quick response! > Seems I forgot to update caffrc.sample :-), but since 2.3-1 caff doesn't > hardcode its own keyserver. Ah, OK. AFAICT, I've been using caff since 2010, so I suppose I shouldn't be surprised that my ~/.caff could use some

Bug#1002880: signing-party: caff defaults to retired pool.sks-keyservers.net

2021-12-30 Thread Guilhem Moulin
Hi, On Thu, 30 Dec 2021 at 17:05:39 -0500, Aaron M. Ucko wrote: > caff has historically defaulted to looking keys up on > pool.sks-keyservers.net $CONFIG{'keyserver'} is deprecated since 2.3-1, and the default is to use the keyserver in ~/.caff/gnupghome/gpg.conf, falling back to the option

Bug#1002880: signing-party: caff defaults to retired pool.sks-keyservers.net

2021-12-30 Thread Aaron M. Ucko
Package: signing-party Version: 2.11-1 Severity: normal caff has historically defaulted to looking keys up on pool.sks-keyservers.net and recommending that signees upload their keys there. However, per https://sks-keyservers.net/, that pool is no longer in service. Could you please substitute