cpu
cpu@hachyderm.io
<p>Recluse open source programmer. Ⓥ. he/him.</p><p><a href="https://hachyderm.io/tags/rust" class="mention hashtag" rel="tag">#<span>rust</span></a> <a href="https://hachyderm.io/tags/go" class="mention hashtag" rel="tag">#<span>go</span></a> <a href="https://hachyderm.io/tags/tls" class="mention hashtag" rel="tag">#<span>tls</span></a> <a href="https://hachyderm.io/tags/dns" class="mention hashtag" rel="tag">#<span>dns</span></a> <a href="https://hachyderm.io/tags/pki" class="mention hashtag" rel="tag">#<span>pki</span></a> <a href="https://hachyderm.io/tags/lpc" class="mention hashtag" rel="tag">#<span>lpc</span></a> <a href="https://hachyderm.io/tags/bikes" class="mention hashtag" rel="tag">#<span>bikes</span></a> <a href="https://hachyderm.io/tags/metal" class="mention hashtag" rel="t
Posts
-
View post
@icing@chaos.social a thing I'm still grieving is the world where when someone reported a bug/vuln it was typically because either A) they were a user of the software, and bumped into the issue B) they thought harder about the code than I had when I wrote it, and found something overlooked. Some combination of those factors helped alleviate the feeling of "damn, I fucked up". I'm all for improving things but the wave of input from drive-by "people" that are both divo...
-
View post
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. This happens for both for true &quot;oh-shit&quot; events, and &quot;cross your t&#39;s dot your i&#39;s&quot; compliance issues and you can&#39;t infer which bucket the incident is in just because issuance has stopped. See https://wiki.mozilla.org/CA/Responding_To_An_Incident#Immediate_Ac...