diff options
| author | Nick Mathewson <nickm@torproject.org> | 2020-01-30 12:56:06 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2020-01-30 12:56:06 -0500 |
| commit | 9662a13d7e587ec9b78af77cdb6607b4ad23a918 (patch) | |
| tree | 64c685a61ae39076064f345598ec88ada2c53937 /ReleaseNotes | |
| parent | ee929eedbb4ca50fef3fbca9066908e8bc6e56fa (diff) | |
| download | tor-9662a13d7e587ec9b78af77cdb6607b4ad23a918.tar.gz tor-9662a13d7e587ec9b78af77cdb6607b4ad23a918.zip | |
Fix a changelog typo
Diffstat (limited to 'ReleaseNotes')
| -rw-r--r-- | ReleaseNotes | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/ReleaseNotes b/ReleaseNotes index c33355f685..7d981e2c42 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -13,7 +13,7 @@ Changes in version 0.4.2.6 - 2020-01-30 - 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 this led to some rules having no effect. libseccomp 2.4.0 changed how rules are generated, leading to a different ordering, which in turn led to a fatal crash during startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by @@ -68,7 +68,7 @@ Changes in version 0.4.1.8 - 2020-01-30 - 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 this led to some rules having no effect. libseccomp 2.4.0 changed how rules are generated, leading to a different ordering, which in turn led to a fatal crash during startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by |