> > Or don't you want to peer with servers having too few keys?
>
> Having too few keys leads to practical problems .. it directly leads to
> excessive resource usage during recon. Having a large delta and not
> catching up is a very good reason to de-peer.
This year my server was dropped from th
Hi!
Gabor Kiss writes:
> Or don't you want to peer with servers having too few keys?
Having too few keys leads to practical problems .. it directly leads to
excessive resource usage during recon. Having a large delta and not
catching up is a very good reason to de-peer.
Christoph
___
Hello,
>> My "limit" is "not-ok"-status on Kristians statistik-page and no update
>> within around 8 to 10 weeks (field "last updated").
> Why do you care if (latest) status OK or not?
> Kristian just marks if a server is pool member or not.
> A server may be excluded from the pool due to several
On 27/09/16 10:58, Danny Horne wrote:
> On 27/09/2016 10:50 am, dirk astrath wrote:
>> I suggest, that everybody checks his own status using
>> sks-keyservers.net/status ... and checks his own "meta"-link
>
> If everyone did this it should clear the 'Servers currently not in the
> pool' section
T
Hello,
> due to cleaning up my peerings key servers which are down for more than
> 4 weeks were depeered.
In general I do the same, but not for 4 weeks ...
My "limit" is "not-ok"-status on Kristians statistik-page and no update
within around 8 to 10 weeks (field "last updated").
While doing a q
Dear dirk,
> My "limit" is "not-ok"-status on Kristians statistik-page and no update
> within around 8 to 10 weeks (field "last updated").
Why do you care if (latest) status OK or not?
Kristian just marks if a server is pool member or not.
A server may be excluded from the pool due to several rea
On 27/09/16 10:50, dirk astrath wrote:
>
> I suggest, that everybody checks his own status using
> sks-keyservers.net/status ... and checks his own "meta"-link:
I wrote a small bash script to do this. You can use your favourite
monitoring tool to invoke it regularly. It returns exit code 0 for
su
On 27/09/2016 10:50 am, dirk astrath wrote:
> I suggest, that everybody checks his own status using
> sks-keyservers.net/status ... and checks his own "meta"-link
If everyone did this it should clear the 'Servers currently not in the
pool' section
signature.asc
Description: OpenPGP digital sign
Hello,
due to cleaning up my peerings key servers which are down for more than
4 weeks were depeered. Further key.cccmz.de was depeered because they do
not answer to mails regarding peering problems.
best regards
Christian Felsing
___
Sks-devel mailing
On 09.02.2015 01:00, Jeremy T. Bouse wrote:
On 07.02.2015 02:08, Christian Felsing wrote:
Hello,
following peerings were removed from key.ip6.li:
sks.undergrid.net
pek1.sks.reimu.io
reason: No crosspeering
best regards
Christian Felsing
As you never contacted me to establish peering with s
On 07.02.2015 02:08, Christian Felsing wrote:
Hello,
following peerings were removed from key.ip6.li:
sks.undergrid.net
pek1.sks.reimu.io
reason: No crosspeering
best regards
Christian Felsing
As you never contacted me to establish peering with sks.undergrid.net
this notice really doesn't
Hello,
following peerings were removed from key.ip6.li:
sks.undergrid.net
pek1.sks.reimu.io
reason: No crosspeering
best regards
Christian Felsing
smime.p7s
Description: S/MIME Cryptographic Signature
___
Sks-devel mailing list
Sks-devel@nongnu.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
due to long time downtimes and no response to clean up announcement
(May, 2nd. 2014), following sks server were depeered from key.ip6.li:
keyserver.cais.rnp.br
keyserver.reinig-it.de
pgp.codelabs.ru
ranger.ky9k.org
best regards
Christian Fels
13 matches
Mail list logo
