<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Let&#39;s Encrypt - malgregator</title>
    <link>https://malgregator.com/tags/lets-encrypt/</link>
    <description>Recent content in Let&#39;s Encrypt on malgregator</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>you@example.com</managingEditor>
    <webMaster>you@example.com</webMaster>
    <lastBuildDate>Thu, 30 Dec 2021 00:00:00 +0000</lastBuildDate>
    
        <atom:link href="https://malgregator.com/tags/lets-encrypt/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Automating Internal Certificate Issuance With ACME-based Certificate Authority</title>
      <link>https://malgregator.com/post/automating-internal-certificate-issuance-with-acme-based-certificate-authority/</link>
      <pubDate>Thu, 30 Dec 2021 00:00:00 +0000</pubDate>
      <author>you@example.com</author>
      <guid>https://malgregator.com/post/automating-internal-certificate-issuance-with-acme-based-certificate-authority/</guid>
      <description>Lessons learned from running Let&#39;s Encrypt Boulder certificate authority software in the company.</description>
    </item><item>
      <title>InfoSec Week 1, 2019</title>
      <link>https://malgregator.com/post/week-1-2019/</link>
      <pubDate>Fri, 04 Jan 2019 08:20:00 +0000</pubDate>
      <author>you@example.com</author>
      <guid>https://malgregator.com/post/week-1-2019/</guid>
      <description>Let&#39;s Encrypt recapitulated the last year in the operation of their ACME based certification authority, and summarized the challenges that they will work on in 2019.   They intend to deploy multi-perspective validation, checking multiple distinct Autonomous Systems for domain validation, preventing potential BGP hijacks. They also plan to run own Certificate Transparency (CT) log.</description>
    </item><item>
      <title>InfoSec Week 32, 2018</title>
      <link>https://malgregator.com/post/week-32-2018/</link>
      <pubDate>Fri, 10 Aug 2018 07:31:00 +0000</pubDate>
      <author>you@example.com</author>
      <guid>https://malgregator.com/post/week-32-2018/</guid>
      <description>A Comcast security flaws exposed more than 26 millions of customers’ personal information. Basically, an attacker could spoof IP address using &#39;X-forwarded-for&#39; header on a Comcast login page and reveal the customer’s location.</description>
    </item><item>
      <title>InfoSec Week 4, 2018</title>
      <link>https://malgregator.com/post/week-04-2018/</link>
      <pubDate>Fri, 26 Jan 2018 18:59:00 +0000</pubDate>
      <author>you@example.com</author>
      <guid>https://malgregator.com/post/week-04-2018/</guid>
      <description>Electron applications designed to run on Windows that register themselves as the default handler for a protocol, like Skype, Slack and others, are vulnerable to the remote code execution vulnerability.</description>
    </item><item>
      <title>InfoSec Week 2, 2018</title>
      <link>https://malgregator.com/post/week-02-2018/</link>
      <pubDate>Thu, 11 Jan 2018 22:11:00 +0000</pubDate>
      <author>you@example.com</author>
      <guid>https://malgregator.com/post/week-02-2018/</guid>
      <description>New research has found a flaw in a group messaging part of a Signal protocol used by Signal, WhatsApp and Threema. It’s hardly exploitable, but the server (attacker) could be, in some theoretical scenario, able to silently join an encrypted group chat.</description>
    </item>
  </channel>
</rss>