<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Reminder that halting issuance is a recommended action during an incident &amp;amp; trustworthy CAs will do it early, until the problem is conclusively identified and remediated.]]></title><description><![CDATA[<p>Reminder that halting issuance is a recommended action during an incident &amp; trustworthy CAs will do it early, until the problem is conclusively identified and remediated.</p><p>This happens for both for true "oh-shit" events, and "cross your t's dot your i's" compliance issues and you can't infer which bucket the incident is in just because issuance has stopped.</p><p>See <br /><a href="https://wiki.mozilla.org/CA/Responding_To_An_Incident#Immediate_Actions" rel="nofollow noopener"><span>https://</span><span>wiki.mozilla.org/CA/Responding</span><span>_To_An_Incident#Immediate_Actions</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/0922a5d2-3974-47f1-ba3b-08bc281345f3/reminder-that-halting-issuance-is-a-recommended-action-during-an-incident-amp-trustworthy-cas-will-do-it-early-until-the-problem-is-conclusively-identified-and-remediated.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 05:50:46 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/0922a5d2-3974-47f1-ba3b-08bc281345f3.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 08 May 2026 21:02:47 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Reminder that halting issuance is a recommended action during an incident &amp;amp; trustworthy CAs will do it early, until the problem is conclusively identified and remediated. on Fri, 08 May 2026 21:09:52 GMT]]></title><description><![CDATA[<p><span><a href="/user/cpu%40hachyderm.io">@<span>cpu</span></a></span> i put certbot in the crontab and hope it doesn't blow up <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>]]></description><link>https://board.circlewithadot.net/post/https://tech.lgbt/users/tay/statuses/116541003698591610</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://tech.lgbt/users/tay/statuses/116541003698591610</guid><dc:creator><![CDATA[tay@tech.lgbt]]></dc:creator><pubDate>Fri, 08 May 2026 21:09:52 GMT</pubDate></item><item><title><![CDATA[Reply to Reminder that halting issuance is a recommended action during an incident &amp;amp; trustworthy CAs will do it early, until the problem is conclusively identified and remediated. on Fri, 08 May 2026 21:06:57 GMT]]></title><description><![CDATA[<p>Also you're renewing your certs early, based on some proportion of their total validity period right? </p><p>And using ACME, so it's automated and easy to fail-over to a standard's compliant alternative CA, right??</p><p>And using ARI so you're informed when you need to re-issue sooner than expected because of a compliance issue, right???</p><p>And back-stopping all of the above with monitoring, right????</p>]]></description><link>https://board.circlewithadot.net/post/https://hachyderm.io/users/cpu/statuses/116540992233711631</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://hachyderm.io/users/cpu/statuses/116540992233711631</guid><dc:creator><![CDATA[cpu@hachyderm.io]]></dc:creator><pubDate>Fri, 08 May 2026 21:06:57 GMT</pubDate></item></channel></rss>