@reto @infosechandbook Using a key server circumvents the admin; you can publish your key without asking them for permission. Isn't that a core value of decentralization? Also having multiple repositories for keys is good. It means even if one repository withholds key updates, they can still be found elsewhere.
@infosechandbook while keys.openpgp.org seems nice, the centralization here is a bit weird.
Wouldn't something like the "Web key directory" be a much better approach to publish our public keys.
For WKD, you need a domain name and files on a server. So, this isn't likely a viable solution for a non-technical user who just wants to publish their OpenPGP key.
Besides, WKD is still a draft, not an official standard. Therefore, some mail clients may not support it, or the implementation differs: https://datatracker.ietf.org/doc/draft-koch-openpgp-webkey-service/
@infosechandbook i can’t get keys.openpgp.org to work in gpg/enig/seahorse. even after removing the conf line in dirmngr suggested in their troubleshooting section.
chaos.social – a Fediverse instance for & by the Chaos community