<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Server on The Penguin Bunker</title><link>https://penguinite.dev/tags/server/</link><description>Recent content in Server on The Penguin Bunker</description><generator>Hugo</generator><language>en-DK</language><copyright>All Rights Reserved.</copyright><lastBuildDate>Fri, 08 May 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://penguinite.dev/tags/server/index.xml" rel="self" type="application/rss+xml"/><item><title>Compilling my own kernel to prevent security vulnerabilities.</title><link>https://penguinite.dev/blog/customkernel/</link><pubDate>Fri, 08 May 2026 00:00:00 +0200</pubDate><guid>https://penguinite.dev/blog/customkernel/</guid><description>&lt;p&gt;This week has honestly been a doozy,
I'm not just talking about the... &amp;quot;socio-economic climate&amp;quot;&lt;sup id="hfda9245a53945bbdfnref:1"&gt;&lt;a href="#hfda9245a53945bbdfn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; we find ourselves in,
but in this week, we've seen two low-privilege escalation bugs, &lt;a href="https://dirtyfrag.io/"&gt;DirtyFrag&lt;/a&gt; and &lt;a href="https://copy.fail/"&gt;CopyFail&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Whenever you hear of a security vulnerability, you've got to first assess if you're impacted at all, that ought to decide the rate at which
you should be patching and mitigating these vulnerabilities.&lt;/p&gt;
&lt;p&gt;You can't treat every bug as a disaster, because some bugs require specific conditions,
these two security vulnerabilities are truly awful, but not for me thankfully.
If you were administering a large shared box, like for instance, a &lt;a href="https://tildeverse.org/"&gt;tilde instance&lt;/a&gt; where you couldn't trust your users, then I'd be panicking!&lt;/p&gt;</description></item></channel></rss>