<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on chuso.net</title>
    <link>https://en.chuso.net/security/</link>
    <description>Recent content in Security on chuso.net</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 18 Nov 2020 20:31:24 +0100</lastBuildDate>
    <atom:link href="https://en.chuso.net/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Trusting invalid SSL certificates is wrong</title>
      <link>https://en.chuso.net/trusting-invalid-ssl-certificates-wrong.html</link>
      <pubDate>Wed, 18 Nov 2020 20:31:24 +0100</pubDate>
      <guid>https://en.chuso.net/trusting-invalid-ssl-certificates-wrong.html</guid>
      <description>&lt;p&gt;So let me put it clear from the first line: trusting invalid certificates is wrong.&lt;/p&gt;&#xA;&lt;p&gt;And now I will explain why it&amp;rsquo;s wrong and why there are few excuses for it.&lt;/p&gt;&#xA;&lt;p&gt;We are talking here about certificates for SSL encryption, which serves basically two purposes:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;em&gt;Privacy&lt;/em&gt; — data is transferred encrypted and can only be decrypted by the intended recipient and not a third party wiretapping the line.&lt;/li&gt;&#xA;&lt;li&gt;&lt;em&gt;Authentication&lt;/em&gt; — making sure the receiving end that will be able to decrypt the data is who they claim to be and data is not diverted to a different receiver by a third party with access to manipulating our transfers.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Invalid certificates obviously defeat the second purpose of verifying the other end&amp;rsquo;s identity:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
