diff options
| author | teor <teor@torproject.org> | 2020-01-30 07:55:12 +1000 |
|---|---|---|
| committer | teor <teor@torproject.org> | 2020-01-30 07:55:12 +1000 |
| commit | 7b6be02a923075ec3966d967cca26eb8d16b645e (patch) | |
| tree | 6c01bb787616622b4bf02ed21e8e4391e6ace905 /changes | |
| parent | 48187248d3f79243590d60285708f3e2d45f8d8f (diff) | |
| parent | 6b392c333a854bb4d18ae6ea1686627451bb03f8 (diff) | |
| download | tor-7b6be02a923075ec3966d967cca26eb8d16b645e.tar.gz tor-7b6be02a923075ec3966d967cca26eb8d16b645e.zip | |
Merge branch 'maint-0.4.1' into maint-0.4.2
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/bug29819 | 8 | ||||
| -rw-r--r-- | changes/bug32778 | 3 |
2 files changed, 11 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. diff --git a/changes/bug32778 b/changes/bug32778 new file mode 100644 index 0000000000..ccb6104692 --- /dev/null +++ b/changes/bug32778 @@ -0,0 +1,3 @@ + o Minor bugfixes (windows service): + - Initialize publish/subscribe system when running as a windows service. + Fixes bug 32778; bugfix on 0.4.1.1-alpha. |