That response means what you uploaded was already on the keyserver so it was
ignored. I also see that key fingerprint on the keyserver, so if it wasn’t
available on keyserver.ubuntu.com and your upload was ignored I’m not sure
how/why it would suddenly be showing up @
https://keyserver.ubuntu.c
I just tried uploading to the ubuntu server. 2024-03-07 18::08 GMT
uploading to the ubuntu server. The response was:
{"inserted":null,"updated":null,"ignored":["rsa4096/05fa40b23af5025974c
3b1a6c62aa8645d00d25b"]}
I will check later if it sticks.
(For proper public access I also updated my key
I would challenge that the ubuntu server is even well maintained for day-to-day
issues currently. My PGP key (0x 949D203A) was uploaded directly to their
server in the past as well as being available on my nodes which they used to
peer with. However, keyserver.ubuntu.com began to intermittently
On 7 Mar 2024, at 16:47, Skip Carter wrote:
>
> I have found that the keyservers are not properly synced:
>
> The MIT server has my key from 2023-03-29
> but the Ubuntu server has only my old expired key 2019-04-10 (4 years
> out of date!).
The MIT server is effectively running unmaintained at
