As I experienced myself (keyoxide/keyoxide-web#199), invalid (malformed) identity claims / notations can cause the error
"No public keys could be fetched using HKP". I added this fact as a new possible issue, along with an appropriate solution and links featuring more
information.
✨ "Something went wrong": Add invalid identity claim as additional HKP error cause #40
gustavblass/keyoxide-docs:main into main
As I experienced myself (keyoxide/keyoxide-web#199), invalid (malformed) identity claims / notations can cause the error "No public keys could be fetched using HKP". I added this fact as a new possible issue, along with an appropriate solution and links featuring more information.
Ironically, the example of a DNS identity claim I gave included a formatting error: It is required to prepend `dns:` to the domain, see: https://docs.keyoxide.org/service-providers/dns/
Instead of exporting a certain PGP key to an .asc file and relying on PGPdump to read it, a batch command can be used directly with GPG: `gpg --batch --command-fd 0 --edit-key julius.eigen@example.org <<< "showpref"`
Use relative links links that are resolved by Zola, instead of hard-coded absolute links. Also, the PGPdump website link is replaced with a link to Keyoxide's docs on listing all identity claims in a PGP key.
@ -15,2 +15,3 @@
:--------------|:---------|:----------------
The key was uploaded to [keys.openpgp.org](https://keys.openpgp.org) but the email address was not verified | Do the first upload to [keys.openpgp.org](https://keys.openpgp.org) via the web interface and confirm the email address via the link in the automatic email | [keyoxide-web#111](https://codeberg.org/keyoxide/keyoxide-web/issues/111)
The key was uploaded to [keys.openpgp.org](https://keys.openpgp.org) but the **email address was not verified** | Do the first upload to [keys.openpgp.org](https://keys.openpgp.org) via the web interface and **confirm the email address** via the link in the automatic email | [keyoxide-web#111](https://codeberg.org/keyoxide/keyoxide-web/issues/111)
The key contains **invalid identity claims**, such as ~`proof@ariadne.id=dns:example.org`~ instead of `proof@ariadne.id=dns:example.org?type=TXT` | **List** all notations present in your key: `gpg --batch --command-fd 0 --edit-key julius.eigen@example.org <<< "showpref"` (insert your own e-mail address or fingerpint). **Check** that each claim is formatted correctly according to [the docs](/service-providers/) on the respective service provider. **[Delete](/openpgp-profiles/gnupg/#Deleting_an_identity_claim)** any invalid notations. | <ul><li>[keyoxide-web#199](https://codeberg.org/keyoxide/keyoxide-web/issues/199#issuecomment-2256716)</li><li>[listing identity claims](/openpgp-profiles/gnupg/#Listing_identity_claims)</ul>
Typo in fingerprint:
(insert your own e-mail address or fingerpint)
I'm not sure how I feel about the alias part of the email here.
Fixed the typo, thanks.
I'm not sure how I feel about the alias part of the email here.
You mean the julius.eigen part? It's a silly math joke referencing the fictitious mathematician Julius Eigen who allegedly invented eigenvalues. 😉 Feel free to insert any e-mail address you deem appropriate :)
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?