Hello, I don't fully understand the permission changes in vboxusb. This ends up setting 0660 (u=rw, g=rw, no x bit) for the /dev/vboxusb directory . I don't see how this can possibly work, as without the x bit I just cannot enter the vboxusb directory nor any files on it. On my Tumbleweed machine at least VirtualBox therefore complains it cannot access USB devices. In addition, we give g+w to the vboxusb dir, which is probably giving too much permission as other vboxusrs can now destroy the contents of this directory.

Is this because of the systemd issue that was fixed in tumbleweed but maybe not in Leap? If so I think only chmoding the files should be fine. (But frankly I would just remove all vboxusb chmod workarounds and file a Leap bug. mknod/chmod randomly failing to set permissions should be treated as an important distro-wide security issue, we should not be silently workarounding it in virtualbox. )