<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Certificates on Project Wintermute</title><link>https://wintermutecore.com/tags/certificates/</link><description>Recent content in Certificates on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 18 Oct 2026 14:14:22 +0000</lastBuildDate><atom:link href="https://wintermutecore.com/tags/certificates/index.xml" rel="self" type="application/rss+xml"/><item><title>go-acme/lego Week in Review: PrimeDNS Provider and an Experimental Conditional DNS Builder</title><link>https://wintermutecore.com/posts/lego-acme-dns-activity-primedns-and-conditional-builder/</link><pubDate>Sun, 18 Oct 2026 14:14:22 +0000</pubDate><guid>https://wintermutecore.com/posts/lego-acme-dns-activity-primedns-and-conditional-builder/</guid><description>&lt;p&gt;go-acme/lego is the ACME client most Go operators reach for when they need certificates issued against Let&amp;rsquo;s Encrypt or any RFC 8555 compliant CA. The past week brought four commits to main, and two of them matter beyond routine maintenance: a new PrimeDNS DNS provider and an experimental feature that changes how the DNS01 challenge can be composed. The dependency updates are the bulk of the diff volume but the least interesting part.&lt;/p&gt;</description></item></channel></rss>