package/libseccomp: security bump to version 2.4.0
authorPeter Korsgaard <peter@korsgaard.com>
Thu, 21 Mar 2019 07:40:43 +0000 (08:40 +0100)
committerPeter Korsgaard <peter@korsgaard.com>
Sun, 24 Mar 2019 08:01:02 +0000 (09:01 +0100)
commit02300786c2fcba2cf641a040a2d87c4022ddb7fc
treece6dfd4c87cfb43999974083f1b4558399583f2f
parentecc2c563696abf584ac78d00c2293648a7cfed89
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>
package/libseccomp/0001-remove-static.patch
package/libseccomp/libseccomp.hash
package/libseccomp/libseccomp.mk