2017-03-13 23:11 GMT+01:00 Simon McVittie <s...@debian.org>: > On Mon, 13 Mar 2017 at 21:58:46 +0100, cgzones wrote: >> Since recently the reference policy defines the file contexts with >> /run prefixes [1] and only supports /var/run via a backward >> compatibility alias. > > Is that backwards compatibility alias available in the stretch version > of the reference policy?
yes > How old is the first reference policy where the /run version works? > > How far in the future is the backwards compatibility alias expected to > go away? idk, there was/is some discussion at the refpolicy mailing list [1] >> Please alter the path from /var/run/dbus/system_bus_socket to >> /run/dbus/system_bus_socket in /usr/lib/systemd/system/dbus.socket to >> avoid wrong file contexts in the future. > > For better or worse, the canonical, interoperable path for the system > bus socket across multiple OS distributions is > /var/run/dbus/system_bus_socket (it has been that since long before > /run was widespread). If /var/run is equivalent to /run, then it shouldn't > matter either way. If /var/run is not equivalent to /run, then the version > we should probably prefer is /var/run. ok, I see also, I found the path /var/run/dbus/system_bus_socket in the official documentation [2] and a similar dbus bugreport [3]. For my part, this can be closed or marked as wont-fix then. Thanks for the quick response. [1] http://oss.tresys.com/pipermail/refpolicy/2017-March/009166.html [2] https://dbus.freedesktop.org/doc/dbus-specification.html#idm2461 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783321
