<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tls on WhyNotHugo</title><link>https://whynothugo.nl/tags/tls/</link><description>Recent content in Tls on WhyNotHugo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 16 Nov 2021 00:07:08 +0100</lastBuildDate><atom:link href="https://whynothugo.nl/tags/tls/posts.xml" rel="self" type="application/rss+xml"/><item><title>Using letsencrypt with HKPK</title><link>https://whynothugo.nl/journal/2016/02/07/using-letsencrypt-with-hkpk/</link><pubDate>Sun, 07 Feb 2016 21:15:40 +0000</pubDate><guid>https://whynothugo.nl/journal/2016/02/07/using-letsencrypt-with-hkpk/</guid><description>HKPK (RFC7469) is a standard that tells browser to cache a certain TLS certificate&amp;rsquo;s signature, and validate that future visits use that certificate (or a defined backup).
I intended on enabling this on my servers, but since letsencrypt renews your certificates every few months, it would mean updating this setting on my nginx configuration. It also means that if something catastrophic happens (like a disk failure), the certificate would be lost, but browsers would still expect to see that same one.</description></item></channel></rss>