<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>cloudflare on {bjørn:johansen}</title>
    <link>https://bjornjohansen.com/tag/cloudflare/</link>
    <description>Recent content in cloudflare on {bjørn:johansen}</description>
    <generator>Hugo -- 0.118.2</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 09 Aug 2018 18:12:42 +0000</lastBuildDate>
    <atom:link href="https://bjornjohansen.com/tag/cloudflare/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Wildcard certificate from Let’s Encrypt with CloudFlare DNS</title>
      <link>https://bjornjohansen.com/wildcard-certificate-letsencrypt-cloudflare/</link>
      <pubDate>Thu, 09 Aug 2018 18:12:42 +0000</pubDate>
       <guid isPermaLink="false">urn:uuid:35613132-6563-5037-b565-393461623230</guid> 
      <description>If you’re using CloudFlare to host your DNS, there is a plugin for the official Let’s Encrypt client Certbot you can use to easily acquire and renew wildcard certificates from Let’s Encrypt.</description>
    </item>
    <item>
      <title>How CloudFlare handled CloudBleed</title>
      <link>https://bjornjohansen.com/how-cloudflare-handled-cloudbleed/</link>
      <pubDate>Fri, 24 Feb 2017 09:27:05 +0000</pubDate>
       <guid isPermaLink="false">urn:uuid:33663066-6334-5466-b930-346639373537</guid> 
      <description>Tavis Ormandy from Google’s Project Zero contacted Cloudflare to report a security problem with their service. It turned out that in some unusual circumstances, they would bleed memory that contained private information.</description>
    </item>
  </channel>
</rss>
