-
libseccomp (2.4.1-0ubuntu0.18.10.3) cosmic-security; urgency=medium
[ Marc Deslauriers ]
* Updated to new upstream 2.4.1 version to fix security issue.
- CVE-2019-9893
* debian/patches/*: removed, all included in new version.
* debian/control: add valgrind to Build-Depends to get more unit tests.
* debian/*.install: change python paths.
* debian/libseccomp2.symbols: added new symbols.
* debian/rules: add dh_auto_configure before dh_auto_install to pick up
all the python versions.
[ Jamie Strandboge ]
* debian/tests/testsuite-live:
- build utils with -pthread
- build tools/scmp_api_level
* debian/tests/src/test-seccomp.c: #include <ctype.h>
* db-properly-reset-attribute-state.patch: db: properly reset the attribute
state in db_col_reset()
-- Jamie Strandboge <email address hidden> Fri, 03 May 2019 20:27:24 +0000
-
libseccomp (2.3.3-3ubuntu1) cosmic; urgency=medium
* Merge from Debian testing. Remaining changes:
- add-log-action.patch: Minimal backport to support the
SECCOMP_RET_LOG action that was released in Linux kernel version
4.14.
- Add autopkgtests.
libseccomp (2.3.3-3) unstable; urgency=medium
* Fix FTBFS: Adapt to renamed README file. (Closes: #902767)
libseccomp (2.3.3-2) unstable; urgency=medium
[ Helmut Grohne ]
* Support the nopython build profile. (Closes: #897057)
[ Felix Geyer ]
* Run upstream "live" tests in an autopkgtest.
libseccomp (2.3.3-1) unstable; urgency=medium
* New upstream release. (Closes: #895417)
- Adds pkey_mprotect syscall. (Closes: #893722)
* Refresh parisc patch.
* Move libseccomp2 back to /usr/lib. (Closes: #894988)
* Make test failures cause the build to fail. (Closes: 877901)
* Build python bindings. (Closes: #810712)
* Switch to debhelper compat level 10.
* Move git repo to salsa.debian.org
* Add myself to Uploaders.
-- Tyler Hicks <email address hidden> Fri, 06 Jul 2018 18:03:38 +0000
-
libseccomp (2.3.1-2.1ubuntu4) bionic; urgency=medium
* debian/tests/data/open.fail_filter: The libseccomp autopkgtests were
failing with glibc 2.27 due to changes in glibc which resulted in
openat() exclusively being used, without any calls to open(). This
resulted in the test process exiting normally instead of being
killed, as was expected. Fix the test failure by removing openat()
from the list of whitelisted syscalls so that the process is killed.
-- Tyler Hicks <email address hidden> Thu, 01 Mar 2018 18:09:19 +0000
