Closed tonyarkles closed 6 years ago
Not sure what led you to believe this repository has anything to do with the site.
Anyhow, that's one of the reasons why the key is available from Bintray as well. I will add an exception for the path on Cloud Flare at a later point.
@michaelklishin the very first yum.repos.d
file recommended in your README.md
points at that file...
@tonyarkles and FWIW it works for most people. We cannot control how/when Cloud Flare does its bot detection magic unless we disable it for a specific path. Feel free to submit a PR for this README, which was in place before Cloud Flare was adopted.
Cloud Flare already has browser integrity check disabled for the key. I cannot immediately think of what else we can do.
Our docs now recommend Bintray over rabbitmq.com downloads in most visible places. We will probably distribute the key together with release artifacts on GitHub as well since we cannot consider Cloud Flare to be reliable for automation tools (at least at the moment) and we want to have a backup option to Bintray that can be used with curl
, wget
and similar (so, not a key server).
Thanks! It definitely tripped me up today when the automation stuff I have set up started randomly failing.
Thanks for all the hard work. We really love how straightforward and reliable RabbitMQ has been for us.
On Dec 11, 2017, at 7:02 PM, Michael Klishin notifications@github.com wrote:
Our docs now recommend Bintray over rabbitmq.com downloads in most visible places. We will probably distribute the key together with release artifacts on GitHub as well since we cannot consider Cloud Flare to be reliable for automation tools (at least at the moment) and we want to have a backup option to Bintray that can be used with curl, wget and similar (so, not a key server).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
When I try to access
https://www.rabbitmq.com/rabbitmq-release-signing-key.asc
from a newly-provisioned DigitalOcean VM, Cloudflare appears to be serving a CAPTCHA to Yum/Curl instead of giving out the signing key.Not sure if this is the right place to post this either. If it's not, please point me in the right direction.