[systemd-bugs] [Bug 83399] New: /dev/fuse wrong permission, chmod in udev rule not applied

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=83399

          Priority: medium
            Bug ID: 83399
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: /dev/fuse wrong permission, chmod in udev rule not
                    applied
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: szunti at gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

I have two computers with Arch Linux and same systemd version (216) and
/dev/fuse has different permissions on them after boot.

One is my old laptop, /dev/fuse is 666 here. So I can use sshfs etc. with every
user.
The other is a newer desktop, and /dev/fuse got 600 permission.

systemctl --version gives:
  systemd 216
  +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +LIBCRYPTSETUP +GCRYPT
+GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN


My investigation:

I see that here is an udev rule in systemd with chmod=0666 in
'50-udev-default.rules', and indeed running on the new computer:

  udevadm trigger -c add -y 'fuse'

fixes the permission to 666.

The /dev/fuse file is created by 'systemd-tmpfiles-setup-dev.service' with
600 permission ('kmod-static-nodes.service' generates the tmpfiles.d config in
'/run/tmpfiles.d/kmod.conf')

I guess it's something with the 'systemd-udev-trigger.service' and the
'systemd-tmpfiles-setup-dev.service' starting simultaneously.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140902/3ff7e2b4/attachment.html>