Re: [Sks-devel] dump-only server (gossip but not public pool availability)

2018-02-04 Thread brent s.
On 02/04/2018 07:45 PM, Chris Kuethe wrote: > you can spin up a second instance on the same host, perhaps bound to > 127.0.0.1:21370 and 127.0.0.1:21371 > . Have your public instance also peer with the > localhost-only instance, and the

Re: [Sks-devel] dump-only server (gossip but not public pool availability)

2018-02-04 Thread Chris Kuethe
you can spin up a second instance on the same host, perhaps bound to 127.0.0.1:21370 and 127.0.0.1:21371. Have your public instance also peer with the localhost-only instance, and the locallhost-only instance peer only with your public instance. Then you can start and stop the localhost-only

Re: [Sks-devel] dump-only server (gossip but not public pool availability)

2018-02-04 Thread brent s.
On 02/04/2018 07:26 PM, Hendrik Visage wrote: > Good day, > >  As I can’t dump the SKS database while running, and the file snapshot > setup not quite feasible for my setup(s) yet, I was wondering about a > gossiping only server (and only gossiping to a limited set servers close > peers) that

Re: [Sks-devel] dump-only server (gossip but not public pool availability)

2018-02-04 Thread Moritz Wirth
Hi, I am not completely sure how new keyservers are determined, one way seems to be the peering list. If you advertise the same hostname on multiple keyservers, only one node will be included (see keys1.flanga.io and keys2.flanga.io are both included in peering lists but only keys.flanga.io as

[Sks-devel] dump-only server (gossip but not public pool availability)

2018-02-04 Thread Hendrik Visage
Good day, As I can’t dump the SKS database while running, and the file snapshot setup not quite feasible for my setup(s) yet, I was wondering about a gossiping only server (and only gossiping to a limited set servers close peers) that isn’t connected/advertised to the SKS pool. This would