NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
133b7a1dd9
kumquat-buildroot/package/libseccomp/0001-remove-static.patch

41 lines
1.3 KiB
Diff
Raw Normal View History

package/libseccomp: security bump to version 2.4.0 >From the advisory: Jann Horn identified a problem in current versions of libseccomp where the library did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE). Jann has done a search using codesearch.debian.net and it would appear that only systemd and Tor are using libseccomp in such a way as to trigger the bad code. In the case of systemd this appears to affect the socket address family and scheduling class filters. In the case of Tor it appears that the bad filters could impact the memory addresses passed to mprotect(2). The libseccomp v2.4.0 release fixes this problem, and should be a direct drop-in replacement for previous v2.x releases. https://www.openwall.com/lists/oss-security/2019/03/15/1 v2.4.0 adds a new scmp_api_level utility, so update 0001-remove-static.patch to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-03-21 08:40:43 +01:00
From 5d010fb06eae43b284e5ccc322f6de47eb42b751 Mon Sep 17 00:00:00 2001
libseccomp: bump to version 2.3.3 - Update patch and sent it upstream - Remove LIBSECCOMP_FIXUP_M4_DIR (not needed anymore) - Add hash for license file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-06 22:33:55 +02:00
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Date: Sat, 2 Jun 2018 13:45:22 +0200
Subject: [PATCH] remove static
Do not force static link of tools, it breaks build with:
package/libseccomp: bump version to 2.2.0 - change upstream URL, project moved to github - removed patches not needed anymore since project switched to autoconf - add newly supported platforms to Config.in [Thomas: - remove hash file, since we're fetching from github now.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-03-29 16:22:28 +02:00
BR2_SHARED_LIBS=y
libseccomp: bump to version 2.3.3 - Update patch and sent it upstream - Remove LIBSECCOMP_FIXUP_M4_DIR (not needed anymore) - Add hash for license file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-06 22:33:55 +02:00
Patch retrieved from
https://git.buildroot.net/buildroot/tree/package/libseccomp/0001-remove-static.patch
and slighly updated to work with 2.3.3
[Upstream status: https://github.com/seccomp/libseccomp/pull/121]
package/libseccomp: bump version to 2.2.0 - change upstream URL, project moved to github - removed patches not needed anymore since project switched to autoconf - add newly supported platforms to Config.in [Thomas: - remove hash file, since we're fetching from github now.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-03-29 16:22:28 +02:00
Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
libseccomp: bump to version 2.3.3 - Update patch and sent it upstream - Remove LIBSECCOMP_FIXUP_M4_DIR (not needed anymore) - Add hash for license file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-06 22:33:55 +02:00
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
package/libseccomp: security bump to version 2.4.0 >From the advisory: Jann Horn identified a problem in current versions of libseccomp where the library did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE). Jann has done a search using codesearch.debian.net and it would appear that only systemd and Tor are using libseccomp in such a way as to trigger the bad code. In the case of systemd this appears to affect the socket address family and scheduling class filters. In the case of Tor it appears that the bad filters could impact the memory addresses passed to mprotect(2). The libseccomp v2.4.0 release fixes this problem, and should be a direct drop-in replacement for previous v2.x releases. https://www.openwall.com/lists/oss-security/2019/03/15/1 v2.4.0 adds a new scmp_api_level utility, so update 0001-remove-static.patch to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-03-21 08:40:43 +01:00
[Peter: updated for v2.4.0 which adds scmp_api_level]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
libseccomp: bump to version 2.3.3 - Update patch and sent it upstream - Remove LIBSECCOMP_FIXUP_M4_DIR (not needed anymore) - Add hash for license file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-06 22:33:55 +02:00
---
package/libseccomp: security bump to version 2.4.0 >From the advisory: Jann Horn identified a problem in current versions of libseccomp where the library did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE). Jann has done a search using codesearch.debian.net and it would appear that only systemd and Tor are using libseccomp in such a way as to trigger the bad code. In the case of systemd this appears to affect the socket address family and scheduling class filters. In the case of Tor it appears that the bad filters could impact the memory addresses passed to mprotect(2). The libseccomp v2.4.0 release fixes this problem, and should be a direct drop-in replacement for previous v2.x releases. https://www.openwall.com/lists/oss-security/2019/03/15/1 v2.4.0 adds a new scmp_api_level utility, so update 0001-remove-static.patch to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-03-21 08:40:43 +01:00
tools/Makefile.am | 3 ---
1 file changed, 3 deletions(-)
package/libseccomp: bump version to 2.2.0 - change upstream URL, project moved to github - removed patches not needed anymore since project switched to autoconf - add newly supported platforms to Config.in [Thomas: - remove hash file, since we're fetching from github now.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-03-29 16:22:28 +02:00
libseccomp: bump to version 2.3.3 - Update patch and sent it upstream - Remove LIBSECCOMP_FIXUP_M4_DIR (not needed anymore) - Add hash for license file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-06 22:33:55 +02:00
diff --git a/tools/Makefile.am b/tools/Makefile.am
package/libseccomp: security bump to version 2.4.0 >From the advisory: Jann Horn identified a problem in current versions of libseccomp where the library did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE). Jann has done a search using codesearch.debian.net and it would appear that only systemd and Tor are using libseccomp in such a way as to trigger the bad code. In the case of systemd this appears to affect the socket address family and scheduling class filters. In the case of Tor it appears that the bad filters could impact the memory addresses passed to mprotect(2). The libseccomp v2.4.0 release fixes this problem, and should be a direct drop-in replacement for previous v2.x releases. https://www.openwall.com/lists/oss-security/2019/03/15/1 v2.4.0 adds a new scmp_api_level utility, so update 0001-remove-static.patch to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-03-21 08:40:43 +01:00
index f768365..5f9d571 100644
libseccomp: bump to version 2.3.3 - Update patch and sent it upstream - Remove LIBSECCOMP_FIXUP_M4_DIR (not needed anymore) - Add hash for license file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-06 22:33:55 +02:00
--- a/tools/Makefile.am
+++ b/tools/Makefile.am
package/libseccomp: security bump to version 2.4.0 >From the advisory: Jann Horn identified a problem in current versions of libseccomp where the library did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE). Jann has done a search using codesearch.debian.net and it would appear that only systemd and Tor are using libseccomp in such a way as to trigger the bad code. In the case of systemd this appears to affect the socket address family and scheduling class filters. In the case of Tor it appears that the bad filters could impact the memory addresses passed to mprotect(2). The libseccomp v2.4.0 release fixes this problem, and should be a direct drop-in replacement for previous v2.x releases. https://www.openwall.com/lists/oss-security/2019/03/15/1 v2.4.0 adds a new scmp_api_level utility, so update 0001-remove-static.patch to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-03-21 08:40:43 +01:00
@@ -37,10 +37,7 @@ scmp_bpf_sim_SOURCES = scmp_bpf_sim.c bpf.h util.h
scmp_api_level_SOURCES = scmp_api_level.c
package/libseccomp: bump version to 2.2.0 - change upstream URL, project moved to github - removed patches not needed anymore since project switched to autoconf - add newly supported platforms to Config.in [Thomas: - remove hash file, since we're fetching from github now.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-03-29 16:22:28 +02:00
scmp_sys_resolver_LDADD = ../src/libseccomp.la
-scmp_sys_resolver_LDFLAGS = -static
scmp_arch_detect_LDADD = ../src/libseccomp.la
-scmp_arch_detect_LDFLAGS = -static
scmp_bpf_disasm_LDADD = util.la
scmp_bpf_sim_LDADD = util.la
package/libseccomp: security bump to version 2.4.0 >From the advisory: Jann Horn identified a problem in current versions of libseccomp where the library did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE). Jann has done a search using codesearch.debian.net and it would appear that only systemd and Tor are using libseccomp in such a way as to trigger the bad code. In the case of systemd this appears to affect the socket address family and scheduling class filters. In the case of Tor it appears that the bad filters could impact the memory addresses passed to mprotect(2). The libseccomp v2.4.0 release fixes this problem, and should be a direct drop-in replacement for previous v2.x releases. https://www.openwall.com/lists/oss-security/2019/03/15/1 v2.4.0 adds a new scmp_api_level utility, so update 0001-remove-static.patch to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-03-21 08:40:43 +01:00
scmp_api_level_LDADD = ../src/libseccomp.la
-scmp_api_level_LDFLAGS = -static
libseccomp: bump to version 2.3.3 - Update patch and sent it upstream - Remove LIBSECCOMP_FIXUP_M4_DIR (not needed anymore) - Add hash for license file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-06 22:33:55 +02:00
--
package/libseccomp: security bump to version 2.4.0 >From the advisory: Jann Horn identified a problem in current versions of libseccomp where the library did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE). Jann has done a search using codesearch.debian.net and it would appear that only systemd and Tor are using libseccomp in such a way as to trigger the bad code. In the case of systemd this appears to affect the socket address family and scheduling class filters. In the case of Tor it appears that the bad filters could impact the memory addresses passed to mprotect(2). The libseccomp v2.4.0 release fixes this problem, and should be a direct drop-in replacement for previous v2.x releases. https://www.openwall.com/lists/oss-security/2019/03/15/1 v2.4.0 adds a new scmp_api_level utility, so update 0001-remove-static.patch to match. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-03-21 08:40:43 +01:00
2.11.0
libseccomp: bump to version 2.3.3 - Update patch and sent it upstream - Remove LIBSECCOMP_FIXUP_M4_DIR (not needed anymore) - Add hash for license file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-06 22:33:55 +02:00
Reference in New Issue Copy Permalink