diff options
| -rw-r--r-- | ChangeLog | 6 | ||||
| -rw-r--r-- | ReleaseNotes | 4 |
2 files changed, 5 insertions, 5 deletions
@@ -9,7 +9,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 @@ -64,7 +64,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 @@ -146,7 +146,7 @@ Changes in version 0.4.3.1-alpha - 2020-01-22 - 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 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 |