Your message dated Thu, 4 Feb 2016 15:33:38 +0100
with message-id <[email protected]>
and subject line Re: Bug#813703: systemd: incorrect permissions on /run/lock
(/var/lock)
has caused the Debian Bug report #813703,
regarding systemd: incorrect permissions on /run/lock (/var/lock)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
813703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813703
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 228-5
Severity: normal
Hi,
The recent update from 228-4 to 228-5 has changed permissions on
/run/lock to 0755 and root:root ownership, whereas before they were
1777
This now makes it impossible to use applications that use said directory
for locking as a non-root user.
I believe the reason is the
d /run/lock 0755 root root -
line in /usr/lib/tmpfiles.d/legacy.conf, which used to be patches in previous
versions.
Cheers,
André
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.113+nmu3
ii libacl1 2.2.52-2
ii libapparmor1 2.10-3
ii libaudit1 1:2.4.5-1
ii libblkid1 2.27.1-3
ii libc6 2.21-7
ii libcap2 1:2.24-12
ii libcap2-bin 1:2.24-12
ii libcryptsetup4 2:1.7.0-2
ii libgcrypt20 1.6.4-5
ii libkmod2 22-1
ii liblzma5 5.1.1alpha+20120614-2.1
ii libmount1 2.27.1-3
ii libpam0g 1.1.8-3.2
ii libseccomp2 2.2.3-2
ii libselinux1 2.4-3
ii libsystemd0 228-5
ii mount 2.27.1-3
ii util-linux 2.27.1-3
Versions of packages systemd recommends:
ii dbus 1.10.6-1
ii libpam-systemd 228-5
Versions of packages systemd suggests:
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
ii udev 228-5
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 228-6
Hello André,
André Draszik [2016-02-04 15:10 +0100]:
> The recent update from 228-4 to 228-5 has changed permissions on
> /run/lock to 0755 and root:root ownership, whereas before they were
> 1777
I noticed this morning too, and uploaded 228-6 to fix this:
systemd (228-6) unstable; 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)
Sorry for the hassle,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
--- End Message ---
