Re: State of the graph

[Andrew Gallagher]

On Tue, 2021-12-14 at 18:53 +0100, Marcel Waldvogel wrote:
> Andrew,
> 
> thanks for the visualization!

NP, it's mostly Gunnar's code. He has a much more extensive history of
the mesh going back nearly three years now, at sks-status.gwolf.org

> I'm feeling flattered that keyserver.trifence.ch is at the center of
> the graph, but this also means it could become a single point of
> failure (and currently, sks.pyro.eu.org is trying to get back up to
> speed and has probably requested ~80k keys in past few hours from
> it).

There has been a distinct increase in churn on the network since it has
become more heterogeneous, and SKS<->Hockeypuck interfaces seem to be
more susceptible to churn than others.

It should be noted that pyro does not suffer from lag, but it appears
cyan on the graph because it only generates stats once per day and the
spider always seems to catch it at a bad time (hence the "?"). Also NB
that fleetstreetops and hnet.se often look like they haven't peered
back with anyone; this is because they are load balanced and only
report their peers 1 in every N scans.

> The green network looks way too much like a star topology with
> keyserver.trifence.ch at the center.

There is a definite centre of gravity to the graph, but it's not quite
as centralised as that! :-) pgpkeys.eu and cyberbits are pretty well
connected also; even if two of those three fell over it wouldn't be
enough to split-brain the mesh.

More worrying are the near-orphaned SKS nodes at the periphery of the
network that remain connected to the core only via other SKS nodes that
are in sync failure. These have been getting a slow trickle of new keys
despite being effectively disconnected; presumably the people
submitting those keys configured their default keyserver back in the
day and are unaware of the apocalypse.

>  It would be great if each of the green (and cyan) nodes could
> connect to one or two of the other nodes with low degrees. Feel free
> to use keybath.trifence.ch, but please also try to get connectivity
> which does not rely on me.

To which I'll add the usual caveat: don't silently add someone as a
peer without asking them to peer back; otherwise it won't work. :-)

A


signature.asc
Description: This is a digitally signed message part

Re: State of the graph

[Marcel Waldvogel]

Andrew,

thanks for the visualization!

I'm feeling flattered that keyserver.trifence.ch is at the center of
the graph, but this also means it could become a single point of
failure (and currently, sks.pyro.eu.org is trying to get back up to
speed and has probably requested ~80k keys in past few hours from it).

The green network looks way too much like a star topology with
keyserver.trifence.ch at the center. It would be great if each of the
green (and cyan) nodes could connect to one or two of the other nodes
with low degrees. Feel free to use keybath.trifence.ch, but please also
try to get connectivity which does not rely on me.

-Marcel

Am Dienstag, dem 14.12.2021 um 08:39 -0800 schrieb Skip Carter:
> It looks like the cluster is collapsing. A year ago I had 18 peers,
> now I have
> 8.
> 
> On Mon, 2021-12-13 at 10:38 +, Andrew Gallagher wrote:
> ...
> > It is now apparent that a significant fraction of otherwise
> > responsive 
> > keyservers are not correctly syncing with any of their peers. These
> > are 
> > indicated in the second graph of
> > https://spider.pgpkeys.eu/graphs by a 
> > 
> 
> 
> 


signature.asc
Description: This is a digitally signed message part

Re: State of the graph

[Martin Dobrev]

Hi guys,

If you’re looking to extend the list of peers and increase the reliability of 
the network, feel free to add me to the list of your peers.

keyserver.dobrev.eu  11370 # Martin Dobrev 
mailto:mar...@dobrev.eu>> 
0x283A56AE9544F3C87C71ADB0CAAAE2B8C198C9AE

And don’t forget to drop me a line to add you back.

Kind regards,
Martin Dobrev

> On 14 Dec 2021, at 16:39, Skip Carter  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> It looks like the cluster is collapsing. A year ago I had 18 peers, now I have
> 8.
> 
> On Mon, 2021-12-13 at 10:38 +, Andrew Gallagher wrote:
> ...
>> It is now apparent that a significant fraction of otherwise responsive 
>> keyservers are not correctly syncing with any of their peers. These are 
>> indicated in the second graph of https://spider.pgpkeys.eu/graphs by a 
>> 
> 
> - -- 
> Dr Everett (Skip) Carter  0x8176163B
> s...@taygeta.com
> Taygeta Scientific Inc
> 607 Charles Ave
> Seaside CA 93955
> 831-641-0645 x103
> 
> -BEGIN PGP SIGNATURE-
> 
> iQGzBAEBCAAdFiEEyBZyWQiIsOIlHndA43NIE4F2FjsFAmG4yMQACgkQ43NIE4F2
> Fjvg7wwAi7sWBdKrU3+VLHZ6JzaDG6hB3iB9lD8N73tomNyJq07R52KjUsksWKhm
> qHUtNmNMYDcoAPDD9CJp/ynlc8OGjjcmfX8dnvMK/8IP9d3SVR3EDJoH04pucPb8
> 85Mh8RApeBEpXkWbitzSEM86VIC9n2ZC7cneHZHJCkvfU5PoyJ7sTCWG1XTRm0po
> o1Ihb02SGobYQGIC/cZeoN70W5sxbCm3tNSaWLA2iGTxg2aJSaHq5J6umrNCKb34
> mBXANsLkoJC9iChpZPBFzx+TgK5DHmrPY7zryuaeFYK40EqOtIDVbvZowqliyxS6
> xIhWUmOnM0xhX4/Zth7QAT6MZMQVNLG+vkqudL4BktdtDIRK3xJ9TN269OYw/Aq4
> UZ6Caf1kg4auWA39+q8wDN+u7pKgpXL4dDDOFfBzsbzNRyhMBXcD1/XtpJmSOS6H
> oqSh4O8NAmUx9/7iuYw6A/fWrmc+ynHPDrHzc2CTq/yXK7U8A3aT+MMhWqR4Nl/0
> 6rNAkWci
> =4Jwd
> -END PGP SIGNATURE-
> 
> 

Re: State of the graph

[Skip Carter]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

It looks like the cluster is collapsing. A year ago I had 18 peers, now I have
8.

On Mon, 2021-12-13 at 10:38 +, Andrew Gallagher wrote:
...
> It is now apparent that a significant fraction of otherwise responsive 
> keyservers are not correctly syncing with any of their peers. These are 
> indicated in the second graph of https://spider.pgpkeys.eu/graphs by a 
> 

- -- 
Dr Everett (Skip) Carter  0x8176163B
s...@taygeta.com
Taygeta Scientific Inc
607 Charles Ave
Seaside CA 93955
831-641-0645 x103

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEEyBZyWQiIsOIlHndA43NIE4F2FjsFAmG4yMQACgkQ43NIE4F2
Fjvg7wwAi7sWBdKrU3+VLHZ6JzaDG6hB3iB9lD8N73tomNyJq07R52KjUsksWKhm
qHUtNmNMYDcoAPDD9CJp/ynlc8OGjjcmfX8dnvMK/8IP9d3SVR3EDJoH04pucPb8
85Mh8RApeBEpXkWbitzSEM86VIC9n2ZC7cneHZHJCkvfU5PoyJ7sTCWG1XTRm0po
o1Ihb02SGobYQGIC/cZeoN70W5sxbCm3tNSaWLA2iGTxg2aJSaHq5J6umrNCKb34
mBXANsLkoJC9iChpZPBFzx+TgK5DHmrPY7zryuaeFYK40EqOtIDVbvZowqliyxS6
xIhWUmOnM0xhX4/Zth7QAT6MZMQVNLG+vkqudL4BktdtDIRK3xJ9TN269OYw/Aq4
UZ6Caf1kg4auWA39+q8wDN+u7pKgpXL4dDDOFfBzsbzNRyhMBXcD1/XtpJmSOS6H
oqSh4O8NAmUx9/7iuYw6A/fWrmc+ynHPDrHzc2CTq/yXK7U8A3aT+MMhWqR4Nl/0
6rNAkWci
=4Jwd
-END PGP SIGNATURE-

Re: State of the graph

[William Hay]

On Mon, Dec 13, 2021 at 10:38:22AM +, Andrew Gallagher wrote:
> Hi, all.
> 
> You may wish to check your own keyserver and contact any of your peers that
> have fallen out of sync with you.
> 
> Thanks,
> A
> 
> -- 
> Andrew Gallagher
> 
Looks like I had a corrupt PTree database that was breaking the recon service.
Rebuilding.

Also a lot of  my peers are semi-defunct.  Adding a few working ones would be 
good:
sks.srv.dumain.com 11370 # William Hay  0xA0B31F88E8123356






signature.asc
Description: PGP signature

State of the graph

[Andrew Gallagher]

Hi, all.

On Tuesday last week, the Ubuntu/Canonical keyservers came back into 
good thermal contact with the SKS mesh, and a large number of updates 
started to circulate. This took a few days to settle down, but as of 
this morning the core of the mesh agrees on a total of ~6.331 million keys.


It is now apparent that a significant fraction of otherwise responsive 
keyservers are not correctly syncing with any of their peers. These are 
indicated in the second graph of https://spider.pgpkeys.eu/graphs by a 
cyan background colour, or equivalently at https://spider.pgpkeys.eu by 
a key count of < 6.3 million.


(Note that both these resources are built from a snapshot in time and 
may therefore contain some inaccuracies).


You may wish to check your own keyserver and contact any of your peers 
that have fallen out of sync with you.


Thanks,
A

--
Andrew Gallagher



OpenPGP_signature
Description: OpenPGP digital signature