Fix for 'gpg: keyserver receive failed: Address not available' and 'g… #349
Conversation
…pg: keyserver receive failed: Operation timed out'
|
Do we really want to disable IPv6 given that some environments go IPv6-only? Using multiple key servers makes sense given how prone they are to attacks. |
|
We don't have this issue in our build system. See our FAQ on gpg: https://github.com/docker-library/faq/tree/b2c55617dc6d924892b4d2599765763915a246aa#openpgp--gnupg-keys-and-verification |
|
It might also be worth having someone with access to info@rabbitmq.com go verify the email for https://keys.openpgp.org so it'll provide the UID and could be used instead (at least for the RabbitMQ half). I'm not sure what the stance of the relevant OpenSSL maintainers is on keys.openpgp.org, but perhaps worth asking? |
|
@tianon done. |
|
@michaelklishin awesome, thanks! I'll get that updated ASAP! 👍 (as part of #354) |
Changes: - docker-library/rabbitmq@d2e5887: Merge pull request docker-library/rabbitmq#354 from infosiftr/latest-toolchain - docker-library/rabbitmq@d38a86a: Update RabbitMQ key fetch to keys.openpgp.org per docker-library/rabbitmq#349 (comment) - docker-library/rabbitmq@a17039e: Switch to the "latest-toolchain" packages
4 participants
Fix for 'gpg: keyserver receive failed: Address not available' and 'gpg: keyserver receive failed: Operation timed out'
Took the workarounds from the following two links.
usbarmory/usbarmory-debian-base_image#9
nodejs/docker-node#380