From: Tollef Fog Heen tfh...@err.no
---
tmpfiles.d/legacy.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tmpfiles.d/legacy.conf b/tmpfiles.d/legacy.conf
index 3219672..a634c17 100644
--- a/tmpfiles.d/legacy.conf
+++ b/tmpfiles.d/legacy.conf
@@ -10,7 +10,7 @@
#
Why do you think this should be changed?
On Wed, Jul 16, 2014 at 12:09 PM, Jon Severinsson j...@severinsson.net wrote:
From: Tollef Fog Heen tfh...@err.no
---
tmpfiles.d/legacy.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tmpfiles.d/legacy.conf
On Wed, Jul 16, 2014 at 1:09 PM, Jon Severinsson j...@severinsson.net wrote:
-d /run/lock 0755 root root -
+d /run/lock 1777 root root -
Won't any user be able to break the system by filling /run, if it has
world-writable directories? IIRC, this was one of the reasons
/run/user/* are separate
onsdagen den 16 juli 2014 12:15:09 skrev du:
Why do you think this should be changed?
Mostly because this is the way it has always been done in Debian, and
changing it breaks some existing init scripts, but I'm ok with continuing to
carry it as a Debian specific patch if it is not considered
]] Jon Severinsson
From: Tollef Fog Heen tfh...@err.no
This one shouldn't be forwarded upstream, /run/lock has historically had
different permissions in Debian and I'd rather get that fixed than
pushing this upstream.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its
