Comment # 8 on bug 1214409 from Giacomo Comes

> That would require a review by the security team.
> 
> All the "enabling" of the service does is create an alias of
> dbus-org.bluez.obex.service to obex.service, which seems weird. Are there
> any other providers of this service? IMO
> /usr/share/dbus-1/services/org.bluez.obex.service needs to be changed to use
> SystemdService=obex.service instead, then no preset needs to be changed.

I think upstream decided to implement
/usr/share/dbus-1/services/org.bluez.obex.service the way it did because the
user then have the option to enable or disable the dbus obex service.
Previously is was always enabled and the user could not disable it (I think).

About the review by the security team, are you sure that it is required?
It is not like a new dbus services is being introduced. In Leap 15.4 the obexd
dbus service was already there and enabled by default. In Leap 15.5 it is
necessary to add: enable obex.service to systemd-presets-common-SUSE to enable
it, but I don't see how the final result is different from Leap 15.4 and why
the security team should be opposed to it.