summaryrefslogtreecommitdiffstats
path: root/package/python-ipython
diff options
context:
space:
mode:
authorPeter Korsgaard <peter@korsgaard.com>2019-03-21 08:40:43 +0100
committerPeter Korsgaard <peter@korsgaard.com>2019-03-27 22:49:59 +0100
commit2fb549c388266c6752712c56d9835343de587aca (patch)
tree983397d2ba579107ffef5ffcaef30e79e82c985a /package/python-ipython
parentb5735379c5713aa994e4bf4209692cb4e0f6e3c8 (diff)
downloadbuildroot-2fb549c388266c6752712c56d9835343de587aca.tar.gz
buildroot-2fb549c388266c6752712c56d9835343de587aca.zip
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> (cherry picked from commit 02300786c2fcba2cf641a040a2d87c4022ddb7fc) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Diffstat (limited to 'package/python-ipython')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud