<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>TLS - Tag - vo.rs</title><link>https://vo.rs/tags/tls/</link><description>TLS - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 11 Dec 2025 16:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/tls/" rel="self" type="application/rss+xml"/><item><title>mTLS: Mutual TLS Between Services Without a Service Mesh</title><link>https://vo.rs/story/mtls-mutual-tls-between-services-without-a-service-mesh/</link><description>&lt;p&gt;Ordinary TLS proves the server&amp;rsquo;s identity to the client. The browser checks the certificate, sees a name it trusts, and gets on with the conversation. The server, meanwhile, has no idea who the client is — it&amp;rsquo;ll talk to anyone. For service-to-service traffic inside your own infrastructure that&amp;rsquo;s backwards. You frequently care far more about &lt;em&gt;which client&lt;/em&gt; is calling than the client cares about the server. Mutual TLS fixes that: both ends present certificates, both ends verify, and an unauthenticated caller never gets past the handshake.&lt;/p&gt;</description><pubDate>Thu, 11 Dec 2025 16:00:00 +0000</pubDate></item><item><title>Let's Encrypt Rate Limits: What to Do When You Hit the Wall</title><link>https://vo.rs/story/lets-encrypt-rate-limits-what-to-do-when-you-hit-the-wall/</link><description>&lt;p&gt;Let&amp;rsquo;s Encrypt is one of the genuinely great things to happen to the open web. Free, automated, universally trusted TLS certificates — the whole reason your homelab services have padlocks now instead of a wall of browser warnings. It is also a free service handling staggering volume, and it protects itself with rate limits. The trouble is you only ever learn those limits exist at the precise moment you slam into one, usually at 2am, usually while debugging something else, usually with a renewal cron job hammering away making everything worse.&lt;/p&gt;</description><pubDate>Wed, 09 Oct 2024 08:00:00 +0000</pubDate></item><item><title>cert-manager: Automated TLS Certificates That Actually Renew</title><link>https://vo.rs/story/cert-manager-automated-tls-certificates-that-actually-renew/</link><description>&lt;p&gt;Everyone who has run a website for more than a year has lived this particular horror. You get an email. The subject line contains the word &amp;ldquo;expires.&amp;rdquo; You ignore it because you&amp;rsquo;re busy. Then on a Sunday morning, the morning, your site is throwing certificate warnings to every visitor and you&amp;rsquo;re SSH&amp;rsquo;d in trying to remember how &lt;code&gt;certbot&lt;/code&gt; works while your coffee goes cold. TLS certificates expire on a schedule that is precisely engineered to be longer than your memory and shorter than your attention span.&lt;/p&gt;</description><pubDate>Tue, 14 May 2024 09:00:00 +0000</pubDate></item></channel></rss>