Ubuntu
gzip package

  1. Bug #1933516
  2. Comment #2

Comment 2 for bug 1933516

Revision history for this message
Dan Streetman (ddstreet) wrote :

> > gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes
> Please could you expand on this? Under what circumstances are users going to be affected by this?

nearly all the systemd services include this setting, e.g.

$ grep -r MemoryDeny *
dbus-org.freedesktop.hostname1.service:MemoryDenyWriteExecute=yes
dbus-org.freedesktop.locale1.service:MemoryDenyWriteExecute=yes
dbus-org.freedesktop.login1.service:MemoryDenyWriteExecute=yes
dbus-org.freedesktop.timedate1.service:MemoryDenyWriteExecute=yes
systemd-hostnamed.service:MemoryDenyWriteExecute=yes
systemd-journald.service:MemoryDenyWriteExecute=yes
systemd-localed.service:MemoryDenyWriteExecute=yes
systemd-logind.service:MemoryDenyWriteExecute=yes
systemd-networkd.service:MemoryDenyWriteExecute=yes
systemd-resolved.service:MemoryDenyWriteExecute=yes
systemd-timedated.service:MemoryDenyWriteExecute=yes
systemd-timesyncd.service:MemoryDenyWriteExecute=yes
systemd-udevd.service:MemoryDenyWriteExecute=yes
udev.service:MemoryDenyWriteExecute=yes

so any call from a systemd service to gzip anything on bionic/ppc64el will fail