<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sysadmin on Left 4 More</title><link>https://left4more.com/tags/sysadmin/</link><description>Recent content in Sysadmin on Left 4 More</description><generator>Hugo</generator><language>en-au</language><lastBuildDate>Sat, 02 May 2026 10:07:32 +1000</lastBuildDate><atom:link href="https://left4more.com/tags/sysadmin/index.xml" rel="self" type="application/rss+xml"/><item><title>CopyFail: Why This Linux Kernel Vuln Should Actually Make You Stop and Think</title><link>https://left4more.com/posts/copyfail-why-this-linux-kernel-vuln-should-actuall/</link><pubDate>Sat, 02 May 2026 10:07:32 +1000</pubDate><guid>https://left4more.com/posts/copyfail-why-this-linux-kernel-vuln-should-actuall/</guid><description>&lt;p>So there&amp;rsquo;s a fresh Linux kernel vulnerability doing the rounds this week — dubbed &lt;strong>CopyFail&lt;/strong> — and if you&amp;rsquo;re running any Linux-based systems at home or at work, it&amp;rsquo;s worth taking a few minutes to understand what&amp;rsquo;s actually going on before you either panic-patch everything or, worse, shrug and do nothing.&lt;/p>
&lt;p>I&amp;rsquo;ve been following the discussion online and it&amp;rsquo;s been&amp;hellip; instructive, in the way that watching people argue about fire safety while standing in a building that may or may not be on fire tends to be.&lt;/p></description></item></channel></rss>