<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Let's Encrypt on Random Musings</title><link>https://chengl.com/tags/lets-encrypt/</link><description>Recent content in Let's Encrypt on Random Musings</description><generator>Hugo</generator><language>en-us</language><copyright>Cheng Long</copyright><lastBuildDate>Sun, 05 Jul 2020 05:49:02 +0000</lastBuildDate><atom:link href="https://chengl.com/tags/lets-encrypt/index.xml" rel="self" type="application/rss+xml"/><item><title>Let's Encrypt Intranet</title><link>https://chengl.com/post/lets-encrypt-intranet/</link><pubDate>Sun, 03 Sep 2017 14:33:24 +0000</pubDate><guid>https://chengl.com/post/lets-encrypt-intranet/</guid><description>&lt;p&gt;&lt;a href="https://letsencrypt.org/"&gt;Let&amp;rsquo;s Encrypt&lt;/a&gt; (LE) has been a popular choice to get certs for public websites. Because it&amp;rsquo;s free and automated. But how to get certs for &lt;strong&gt;private&lt;/strong&gt; websites, which are common in company&amp;rsquo;s intranet?&lt;/p&gt;
&lt;h2 id="problem"&gt;Problem&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;There&amp;rsquo;s a web app in your company&amp;rsquo;s intranet.&lt;/li&gt;
&lt;li&gt;The web app has a fully qualified domain name (FQDN), e.g. &lt;strong&gt;foo.example.com&lt;/strong&gt;, not an internal one like &lt;strong&gt;foo.internal&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;It only resolves to a private IP behind VPN. Therefore, it&amp;rsquo;s inaccessible without a valid VPN.&lt;/li&gt;
&lt;li&gt;You want to add an extra layer of security by enabling HTTPS.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;How to get a cert for it? And how to automate it and get it for free?&lt;/p&gt;</description></item><item><title>Let's Encrypt Nginx</title><link>https://chengl.com/post/lets-encrypt-nginx/</link><pubDate>Sun, 31 Jan 2016 08:41:00 +0000</pubDate><guid>https://chengl.com/post/lets-encrypt-nginx/</guid><description>&lt;p&gt;&lt;em&gt;Update [2017 Aug 5]: Certbot has been developed by EFF and others as an easy-to-use automatic client that fetches and deploys SSL/TLS certificates. I would recommend using &lt;a href="https://certbot.eff.org/"&gt;it&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="why"&gt;Why&lt;/h2&gt;
&lt;p&gt;Since you are here, you probably know what &lt;a href="https://letsencrypt.org"&gt;Let&amp;rsquo;s Encrypt&lt;/a&gt; is and why it exists. If not, below is an executive summary (copied from &lt;a href="https://letsencrypt.org/howitworks/"&gt;here&lt;/a&gt;):&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Anyone who has gone through the trouble of setting up a secure website knows what a hassle getting and maintaining a certificate can be. Let’s Encrypt automates away the pain and lets site operators turn on and manage HTTPS with simple commands.&lt;/p&gt;</description></item></channel></rss>