-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DBus: not reading /etc/machine-id breaks DBus GetMachineId #143
Comments
Interestingly it seems that (outside sanbox) you can ask machine id from any other dbus service but dbus daemon itself - I wonder if the method / whole peer interface has been blocked on purpose and what that purpose might be? Anyway, regarding sailjail: Is there some rationale for hiding machine-id file? @Tomin1 @rainemak Any thoughts? |
They are world-readable in general.
Of course the very privacy-conscious may argue that access to something that allows to uniquely identify the device a user is running on is something that needs to be prevented. Sailfish OS may opt to declare itself "stateless" for this case (man machine-id)
... but that is a design decision for systemd (and has consequences for its behaviour). |
This might be the best idea here. To use |
Steps to reproduce:
service org.example.MyApp
,path /org/example/MyApp
,iface org.example.MyApp
), and necessary settings in .desktopExec=sailfish-qml harbour-myapp
)busctl --user introspect org.example.MyApp /org/example/MyApp
Ping
andGetMachineId
are listed under nameorg.freedesktop.DBus.Peer
busctl --user call org.example.MyApp org.example.MyApp org.freedesktop.DBus.Peer GetMachineId
/etc/machine-id
is available and set up correctly outside the box.I suggest to add the following around here:
unless there are concerns about privacy or security about
/etc/machine-id
.I realize that this is probably not a critical interface, however maybe in inspecting this other issues regarding FDO expectations are found.
The text was updated successfully, but these errors were encountered: