diff options
| author | teor <teor@torproject.org> | 2020-01-30 07:54:58 +1000 |
|---|---|---|
| committer | teor <teor@torproject.org> | 2020-01-30 07:54:58 +1000 |
| commit | 65825018c7aed931324dd427bb1e84544a9b2f47 (patch) | |
| tree | 197a39f51c233283baa67d166262571a8c85bc68 /changes | |
| parent | 026f068bb3aed9de0f1cc6792f6c9528b7b27db2 (diff) | |
| parent | 41d52e9cd80bfb318ec7f0969f3889d275012e37 (diff) | |
| download | tor-65825018c7aed931324dd427bb1e84544a9b2f47.tar.gz tor-65825018c7aed931324dd427bb1e84544a9b2f47.zip | |
Merge branch 'maint-0.3.5' into maint-0.4.0
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. |