summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorDebarshi Ray <debarshir@gnome.org>2019-07-22 21:30:25 +0200
committerLennart Poettering <lennart@poettering.net>2019-07-24 16:41:45 +0200
commit90ce7627dfe824ff6e7c0ca5f96350fbcfec7118 (patch)
treef4f7e5bd10466d2cf6764fe6dbfed67ec2e8a30c /NEWS
parent181824e32c87934cea8130cb5652a6a2ded842a2 (diff)
downloadsystemd-90ce7627dfe824ff6e7c0ca5f96350fbcfec7118.tar.gz
sysctl: Enable ping(8) inside rootless Podman containers
This makes ping(8) work without CAP_NET_ADMIN and CAP_NET_RAW because those aren't effective inside rootless Podman containers. It's quite useful when using OSTree based operating systems like Fedora Silverblue, where development environments are often set up using rootless Podman containers with helpers like Toolbox [1]. Not having a basic network utility like ping(8) work inside the development environment can be inconvenient. See: https://lwn.net/Articles/422330/ http://man7.org/linux/man-pages/man7/icmp.7.html https://github.com/containers/libpod/issues/1550 The upper limit of the range of group identifiers is set to 2147483647, which is 2^31-1. Values greater than that get rejected by the kernel because of this definition in linux/include/net/ping.h: #define GID_T_MAX (((gid_t)~0U) >> 1) That's not so bad because values between 2^31 and 2^32-1 are reserved on systemd-based systems anyway [2]. [1] https://github.com/debarshiray/toolbox [2] https://systemd.io/UIDS-GIDS.html#summary
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS6
1 files changed, 6 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index ced3b5c044..eecf26c511 100644
--- a/NEWS
+++ b/NEWS
@@ -2,6 +2,12 @@ systemd System and Service Manager
CHANGES WITH 243 in spe:
+ * Enable unprivileged programs, neither setuid nor having file
+ capabilities, to send ICMP Echo requests by turning on the
+ net.ipv4.ping_group_range parameter of the Linux kernel for all
+ groups. If this is not desirable, then it can be disabled by setting
+ the parameter to "1 0".
+
* Previously, filters defined with SystemCallFilter= would have the
effect that an calling an offending system call would terminate the
calling thread. This behaviour never made much sense, since killing