<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SSL on iMil.net</title>
    <link>http://imil.net/blog/tags/ssl/</link>
    <description>Recent content in SSL on iMil.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Mar 2020 08:28:40 +0000</lastBuildDate>
    <atom:link href="http://imil.net/blog/tags/ssl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Let&#39;s Encrypt certificates using LEGO</title>
      <link>http://imil.net/blog/posts/2020/let-s-encrypt-certificates-using-lego/</link>
      <pubDate>Mon, 02 Mar 2020 08:28:40 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2020/let-s-encrypt-certificates-using-lego/</guid>
      <description>&lt;p&gt;This post is more like a self-reminder on how I setup automatic SSL/TLS certificate renewal on my servers.&lt;/p&gt;&#xA;&lt;p&gt;I chose &lt;a href=&#34;https://go-acme.github.io/lego&#34;&gt;LEGO&lt;/a&gt; to handle my certificates renewal with &lt;a href=&#34;https://letsencrypt.org/&#34;&gt;Let&amp;rsquo;s Encrypt&lt;/a&gt; because it&amp;rsquo;s simple to use, has no dependency, great documentation and is worked on at a constant pace.&lt;/p&gt;&#xA;&lt;p&gt;I found &lt;a href=&#34;https://code.kuederle.com/letsencrypt/&#34;&gt;this&lt;/a&gt; and &lt;a href=&#34;https://dddpaul.github.io/blog/2016/10/20/lego-nginx/&#34;&gt;this&lt;/a&gt; articles very useful, but they are outdated in their use of the &lt;code&gt;tls&lt;/code&gt; and &lt;code&gt;http&lt;/code&gt; parameters. So here are my notes.&lt;/p&gt;&#xA;&lt;p&gt;This procedure is &lt;em&gt;Debian GNU/Linux&lt;/em&gt; based but I also used it pretty much as-is on &lt;em&gt;NetBSD&lt;/em&gt; and &lt;em&gt;FreeBSD&lt;/em&gt;, only &lt;code&gt;nginx&lt;/code&gt; related &lt;code&gt;PATH&lt;/code&gt;s changed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Alpine et les certificats SSL</title>
      <link>http://imil.net/blog/posts/2010/alpine-et-les-certificats-ssl/</link>
      <pubDate>Sat, 27 Feb 2010 20:46:50 +0000</pubDate>
      <guid>http://imil.net/blog/posts/2010/alpine-et-les-certificats-ssl/</guid>
      <description>&lt;p&gt;Je sais, je suis un vieux con. Et en bon vieux con que je suis, je n&amp;rsquo;ai jamais réussi à utiliser un autre &lt;a href=&#34;http://en.wikipedia.org/wiki/Mail_User_Agent&#34;&gt;MUA&lt;/a&gt; que &lt;a href=&#34;http://www.washington.edu/pine/&#34;&gt;pine&lt;/a&gt; / &lt;a href=&#34;http://www.washington.edu/alpine/&#34;&gt;alpine&lt;/a&gt;. C&amp;rsquo;est pas qu&amp;rsquo;il soit franchement au dessus des autres, loin s&amp;rsquo;en faut, mais que voulez-vous, on ne change pas 14 ans d&amp;rsquo;habitudes comme ça.&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Alpine&lt;/em&gt; a des avantages, mais aussi beaucoup d&amp;rsquo;inconvénients, et l&amp;rsquo;un d&amp;rsquo;entre eux, c&amp;rsquo;est la manière dont il &amp;ldquo;gère&amp;rdquo; la validité des certificats &lt;a href=&#34;http://fr.wikipedia.org/wiki/Secure_Sockets_Layer&#34;&gt;TLS/SSL&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
