-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider implementing explicit API support for keys.openpgp.org #294
Comments
Given that sks-keyservers flagged themselves as legacy and are about to die out, we probably should just remove their support and focus on explicitly supporting the newer API. |
https://www.reddit.com/r/crypto/comments/o7oh4w/skskeyserversnet_pool_dns_records_disabled/
|
@theseer Please remove SKS from source and docs. Temporarily we could use |
You lost me: What does sks-keyservers have to do with the API provided by keys.openpgp.org?
What do you mean and why "temporarily"? |
|
Given the DNS does no longer resolve, this is basically a no-op. On top: SKS-Keyserver already are the last resort entry (see: https://github.com/phar-io/phive/blob/master/conf/pgp-keyservers.php) and basically shouldn't be reached in 99,9% of all cases. We indeed should remove sks references from the phar.io website. |
I see! :) |
I know what And it's a lot more than just an alternative, also providing a different API. Hence, this ticket. Using keys.openpgp.org is NOT a temporary option. The key handling is different and not all keys that are (or by now were) listed in sks' servers are available on openpgp.org yet. Again, nothing to do with this issue at all: This is about implementing explicit support for the keys.openpgp.org provided API. |
Currently we use the "compat api" that mimiks the API provided by sks-keyservers.
/cc @jaapio
The text was updated successfully, but these errors were encountered: