<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>📎 Appendix on Deevnet IoTaaS</title><link>https://deevnet.github.io/deevnet-docs/docs/appendix/</link><description>Recent content in 📎 Appendix on Deevnet IoTaaS</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://deevnet.github.io/deevnet-docs/docs/appendix/index.xml" rel="self" type="application/rss+xml"/><item><title>Cryptography and PKI Primer</title><link>https://deevnet.github.io/deevnet-docs/docs/appendix/cryptography-and-pki-primer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/appendix/cryptography-and-pki-primer/</guid><description>&lt;h1 id="cryptography-and-pki-primer">
 Cryptography and PKI Primer
 &lt;a class="anchor" href="#cryptography-and-pki-primer">#&lt;/a>
&lt;/h1>
&lt;p>Every secure connection solves the same problem: talking privately to a machine you have never met,
over a network that anyone along the way can read and alter. Encryption hides the conversation, but
it can&amp;rsquo;t tell you &lt;em>who&lt;/em> is on the other end. That is the job of a &lt;strong>public key infrastructure
(PKI)&lt;/strong>: certificates that bind names to keys, signed by &lt;strong>certificate authorities (CAs)&lt;/strong> that you
decided to trust ahead of time. The protocol that puts it all to work on a connection is &lt;strong>TLS&lt;/strong>,
the &amp;ldquo;S&amp;rdquo; in HTTPS. This page builds TLS and PKI up one idea at a time, with no math. It ends with why
the web&amp;rsquo;s PKI is invisible to almost everyone, and why a private network like Deevnet runs its own.&lt;/p></description></item></channel></rss>