diff options
| author | Peter Gerber <peter@arbitrary.ch> | 2019-06-10 14:56:31 +0200 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2019-12-17 09:47:28 -0500 |
| commit | 0d64bafcfedd259fb15b3ee85a7b00a840aec73b (patch) | |
| tree | 4234a4e7a82ddd363a4bd90bdc6f5e4fe7a6a5ac /changes | |
| parent | 1cd20ff848eab6ee7b441c5aab0578ab02a114bc (diff) | |
| download | tor-0d64bafcfedd259fb15b3ee85a7b00a840aec73b.tar.gz tor-0d64bafcfedd259fb15b3ee85a7b00a840aec73b.zip | |
Correct how we use libseccomp
This fixes a startup crash with libseccomp v2.4.0 if Sandbox is
set to 1.
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/bug29819 | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/changes/bug29819 b/changes/bug29819 new file mode 100644 index 0000000000..d37ac83d66 --- /dev/null +++ b/changes/bug29819 @@ -0,0 +1,8 @@ + o Minor bugfixes (linux seccomp sandbox): + - Correct how we use libseccomp. Particularly, stop assuming that + rules are applied in a particular order or that more rules are + processed after the first match. Neither is the case! In libseccomp + <2.4.0 this lead to some rules having no effect. Libseccomp 2.4.0 + changed how rules are generated leading to a different ordering + which in turn lead to a fatal crash during startup. Fixes bug + 29819; bugfix on 0.2.5.1-alpha. Patch by Peter Gerber. |