<?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[While #NixOS should not be affected by #CopyFail as it uses recent kernels, here are additional fixes you can apply:]]></title><description><![CDATA[<p>While <a href="https://tux.social/tags/NixOS" rel="tag">#<span>NixOS</span></a> should not be affected by <a href="https://tux.social/tags/CopyFail" rel="tag">#<span>CopyFail</span></a> as it uses recent kernels, here are additional fixes you can apply:</p><p>Disabling setuid does not mitigate it, but reduces the attack surfaces overall significantly.</p><p>Instead of <a href="https://tux.social/tags/sudo" rel="tag">#<span>sudo</span></a>, <a href="https://tux.social/tags/su" rel="tag">#<span>su</span></a>, <a href="https://tux.social/tags/pkexec" rel="tag">#<span>pkexec</span></a> and other <a href="https://tux.social/tags/setuid" rel="tag">#<span>setuid</span></a> binaries you can use <a href="https://tux.social/tags/run0" rel="tag">#<span>run0</span></a> or a dedicated root account.</p><p>I have disabled setuid for a bunch of binaries I don't need, they still work when ran as root, with run0 or <a href="https://tux.social/tags/sudo" rel="tag">#<span>sudo</span></a>-rs.</p><p>```nix<br />boot.blacklistedKernelModules = [<br />    "algif_aead"<br />];</p><p>security.sudo.enable = false;</p><p>security.wrappers = {<br />    su.enable = false;<br />    pkexec.enable = false;<br />    <br />    # example setuid binary<br />    chsh = {<br />        source = "${pkgs.shadow}/bin/chsh";<br />        setuid = lib.mkForce false;<br />        owner = "root";<br />        group = "root";<br />    };<br />};<br />```</p>]]></description><link>https://board.circlewithadot.net/topic/30b8b80a-4e6d-48a7-8b1b-cc0645f067ab/while-nixos-should-not-be-affected-by-copyfail-as-it-uses-recent-kernels-here-are-additional-fixes-you-can-apply</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 22:32:44 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/30b8b80a-4e6d-48a7-8b1b-cc0645f067ab.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 01 May 2026 13:15:21 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to While #NixOS should not be affected by #CopyFail as it uses recent kernels, here are additional fixes you can apply: on Fri, 01 May 2026 14:22:41 GMT]]></title><description><![CDATA[<p><span><a href="https://chaos.social/@marie">@<span>marie</span></a></span> <span><a href="/user/rhababerbarbar%40tux.social">@<span>Rhababerbarbar</span></a></span> Also, almost no one is going to be running the vulnerable kernel module anyways unless they compiled a monolithic kernel so..., yeah, feels pretty overblown to me.</p>]]></description><link>https://board.circlewithadot.net/post/https://social.zerojay.com/users/jay/statuses/116499766419396690</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://social.zerojay.com/users/jay/statuses/116499766419396690</guid><dc:creator><![CDATA[jay@social.zerojay.com]]></dc:creator><pubDate>Fri, 01 May 2026 14:22:41 GMT</pubDate></item><item><title><![CDATA[Reply to While #NixOS should not be affected by #CopyFail as it uses recent kernels, here are additional fixes you can apply: on Fri, 01 May 2026 13:27:20 GMT]]></title><description><![CDATA[<p><span><a href="/user/rhababerbarbar%40tux.social">@<span>Rhababerbarbar</span></a></span> setuid binaries have nothing to do with the vulnerability, they are just an easy way of exploiting it. Avoiding them does not make you less vulnerable to copyfail. (blacklisting the kernel module is good)</p>]]></description><link>https://board.circlewithadot.net/post/https://chaos.social/users/marie/statuses/116499548771780034</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://chaos.social/users/marie/statuses/116499548771780034</guid><dc:creator><![CDATA[marie@chaos.social]]></dc:creator><pubDate>Fri, 01 May 2026 13:27:20 GMT</pubDate></item></channel></rss>