Changeset d16c71a

Timestamp:

08/26/2022 02:48:29 AM (20 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/soup3, xry111/xf86-video-removal

Children:

7484ed9

Parents:

8a2cb97

git-author:

Xi Ruoyao <xry111@…> (08/26/2022 02:19:40 AM)

git-committer:

Xi Ruoyao <xry111@…> (08/26/2022 02:48:29 AM)

Message:

dhcpcd: work around seccomp issue introduced by glibc-2.36

To me a seccomp filter as a strict allowlist with SECCOMP_RET_KILL is
simply wrong [1]. But for now simply work around the issue.

Editors should rebuild dhcpcd with the sed. Revert the tag so another
editor can verify the change.

No packages depends on dhcpcd. The only packages mentioning dhcpcd are
NetworkManager and wpa_supplicant. NM doesn't support dhcpcd-9.0 or later
at all, and wpa_supplicant only refers to dhcpcd so a user can get the
IP address from AP after configured wpa_supplicant.

[1]: ​https://github.com/NetworkConfiguration/dhcpcd/issues/120#issuecomment-1227980583

File:

• networking/connect/dhcpcd.xml (modified) (2 diffs)

networking/connect/dhcpcd.xml

@@ -44 +44 @@
     </para>
 
-    &lfs112_checked;
+    &lfs111_checked;
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
@@ -114 +114 @@
          -u 52 dhcpcd &amp;&amp;
 chown    -v dhcpcd:dhcpcd /var/lib/dhcpcd </userinput></screen>
+
+    <para>Fix a runtime error caused by a change in glibc-2.36:</para>
+
+<screen><userinput>sed '/Deny everything else/i SECCOMP_ALLOW(__NR_getrandom),' \
+    -i src/privsep-linux.c</userinput></screen>
 
     <para>