From: Etienne Dechamps <etienne@edechamps.fr>
Date: Wed, 2 Aug 2023 17:52:41 +0000 (+0100)
Subject: NEWS: PrivateNetwork implies PrivateMounts
X-Git-Tag: v255-rc1~842
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=6b2d576f2b38c0385bb056af328754ec8966f9fd;p=thirdparty%2Fsystemd.git

NEWS: PrivateNetwork implies PrivateMounts

This is clearly a change that can break existing units, and broke my
system in at least two different ways. For this reason this should have
been added to NEWS in #26458, specifically c2da3bf, but wasn't.
---

diff --git a/NEWS b/NEWS
index 3b05a0ecf99..fe046fe6151 100644
--- a/NEWS
+++ b/NEWS
@@ -73,6 +73,9 @@ CHANGES WITH 254:
           trailing with escape as a non comment line. For details, see:
           https://github.com/systemd/systemd/issues/27975
 
+        * PrivateNetwork=yes and NetworkNamespacePath= now imply
+          PrivateMounts=yes unless PrivateMounts=no is explicitly specified.
+
         * Behaviour of sandboxing options for the per-user service manager
           units has changed. They now imply PrivateUsers=yes, which means user
           namespaces will be implicitly enabled when a sandboxing option is