This blog not affected by the memory-leak of Cloudflare

In the post 'Implementing https on Blogger using Cloudflare' I describe how I utilize Cloudflare services to protect this blog. Unfortunately, we all noticed that Cloudflare has suffered from a tremendous memory-leak which was announced Friday, February the 24th.

This leak (a bit referred to as #cloudbleed) is extensively covered in the following posts.

• Cloudflare - Incident report on memory leak caused by Cloudflare parser bug
  https://blog.cloudflare.com/incident-report-on-memory-leak-caused-by-cloudflare-parser-bug/
• ARS Techinca - Serious Cloudflare bug exposed a potpourri of secret customer data
  https://arstechnica.com/security/2017/02/serious-cloudflare-bug-exposed-a-potpourri-of-secret-customer-data/
• Chromium Bug Tracker - Cloudflare Reverse Proxies are Dumping Uninitialized Memory
  https://bugs.chromium.org/p/project-zero/issues/detail?id=1139
• Pirate (GitHub) - List of Sites possibly affected by Cloudflare's #Cloudbleed HTTPS Traffic Leak
  https://github.com/pirate/sites-using-cloudflare

On February the 24th I also got confirmation that this blog has not been affected by the memory leak in the html-parser of Cloudflare.

So, no worries in that regard concerning this blog.