CloudFlare states Adafruit not part of the @Cloudflare issue(s) #cloudbleed @adafruit
tl;dr CloudFlare has stated that Adafruit’s sites were *NOT* part of the CloudFlare issues.
Adafruit uses CloudFlare’s proxy service to reduce server load and provide a faster browsing experience for customers using the Adafruit blog and shop.
CoudFlare announced that a major leak was detected in their network which affected a number of sites using their proxy service (https://blog.cloudflare.com/incident-report-on-memory-leak-caused-by-cloudflare-parser-bug/).
According to CloudFlare, only a small number of sites were affected. After contacting them, CloudFlare engineering confirmed that *NONE* of Adafruit’s domains were in the affected zones.
== EMAIL FROM CLOUDFLARE = REDACTED NAME
(Cloudflare)
Feb 24, 5:49 PM GMT
Hi, Thanks for contacting Cloudflare Customer Support. We have notified all the customers the were affected by the memory leak and I can confirm the zones on your account were not one of them. Our CTO John Graham-Cumming has published all of the information we have here:
Please let us know if you have any other questions.
Kind Regards,
– Cloudflare Senior Support Engineer
=
Adafruit takes protecting your data very seriously, we took the following steps in an abundance of caution:
Disabled CloudFlare proxy service on the Adafruit Accounts system.
To defend against the possibility that active session cookies were leaked, we closed all active user sessions across Adafruit’s websites.
We suggest:
Check the list of potentially affected sites (https://github.com/pirate/sites-using-cloudflare) and change your password for any of those sites.
Change your passwords (we always recommend that you use strong and unique passwords for each site that you use; please don’t reuse your Adafruit website anywhere else).
Adafruit has made a pull request to the folks that list us on the “sites-using-cloudflare” (https://github.com/pirate/sites-using-cloudflare) list including the note from CloudFlare support indicating that we were not affected by the memory leak.
Adafruit publishes a wide range of writing and video content, including interviews and reporting on the maker market and the wider technology world. Our standards page is intended as a guide to best practices that Adafruit uses, as well as an outline of the ethical standards Adafruit aspires to. While Adafruit is not an independent journalistic institution, Adafruit strives to be a fair, informative, and positive voice within the community – check it out here: adafruit.com/editorialstandards
Stop breadboarding and soldering – start making immediately! Adafruit’s Circuit Playground is jam-packed with LEDs, sensors, buttons, alligator clip pads and more. Build projects with Circuit Playground in a few minutes with the drag-and-drop MakeCode programming site, learn computer science using the CS Discoveries class on code.org, jump into CircuitPython to learn Python and hardware together, TinyGO, or even use the Arduino IDE. Circuit Playground Express is the newest and best Circuit Playground board, with support for CircuitPython, MakeCode, and Arduino. It has a powerful processor, 10 NeoPixels, mini speaker, InfraRed receive and transmit, two buttons, a switch, 14 alligator clip pads, and lots of sensors: capacitive touch, IR proximity, temperature, light, motion and sound. A whole wide world of electronics and coding is waiting for you, and it fits in the palm of your hand.
Have an amazing project to share? The Electronics Show and Tell is every Wednesday at 7pm ET! To join, head over to YouTube and check out the show’s live chat – we’ll post the link there.
Python for Microcontrollers — Python on Microcontrollers Newsletter: MicroPython Pico W Bluetooth, CircuitPython 8.0.4 and much more! #CircuitPython #Python #micropython @ThePSF @Raspberry_Pi
