Public bug reported:

Upstream regressed systemd sandboxing in memcached 1.5.6 by commenting
out '##safer##'-prefixed lines and expecting packaging to uncomment them
when using a newer version of systemd that supports these lines (which
we already do).

I have reported this upstream in

In the meantime, we need to patch these comments back out (re-enabling
the lines). Christian Ehrhardt also suggested to me that it would be a
good idea to make sure that no '##safer##' get through in case upstream
add any more through a check in debian/rules.

I'm creating this bug to document what's going on so that I can link to
this from this workaround in the packaging. We should be able to drop
this workaround as soon as this is resolved upstream.

** Affects: memcached
     Importance: Unknown
         Status: Unknown

** Affects: memcached (Ubuntu)
     Importance: Medium
         Status: Triaged

** Bug watch added: #359

** Also affects: memcached via
   Importance: Unknown
       Status: Unknown

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  memcached.service is less secure by default

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to