Ubuntu
systemd package

wrong /run/lock permissions

Bug #1541775 reported by Sebastien Bacher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Debian)
Fix Released
Unknown
systemd (Ubuntu)
Fix Released
Critical
Martin Pitt
Ubuntu ubuntu-16.02

Bug Description

Using current xenial it seems the /run/lock permissions are wrong

drwxr-xr-x 6 root root 140 févr. 4 11:23 /run/lock

it should be 1777

Martin Pitt (pitti)
Changed in systemd (Ubuntu):
importance: Undecided → Critical
status: New → In Progress
assignee: nobody → Martin Pitt (pitti)
milestone: none → ubuntu-16.02
Martin Pitt (pitti)
Changed in systemd (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemd - 228-5ubuntu2

---------------
systemd (228-5ubuntu2) xenial; urgency=medium

  * Make-run-lock-tmpfs-an-API-fs.patch: Drop /run/lock from
    tmpfiles.d/legacy.conf to avoid the latter clobbering the permissions of
    /run/lock. Fixes fallout from cleanup in -5 that resulted /run/lock to
    have 0755 permissions instead of 1777. (LP: #1541775)

 -- Martin Pitt <email address hidden> Thu, 04 Feb 2016 11:53:05 +0100

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in systemd (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.