Comment # 10 on bug 1202059 from Imobach Gonzalez Sosa

Hi Matthias,

Thanks a lot for having a look!

(In reply to Matthias Gerstner from comment #9)
> I had a quick first look at the integration found in
> YaST:Head:D-Installer/rubygem-d-installer labeled with version 0.4.2-2.5.
> 
> The D-Bus interface looks pretty large and dynamic. Since this is for
> installing Linux onto the host the security posture for it probably will be
> different than for regular D-Bus services. The clients of this D-Bus service
> will have root-like power, if I am not mistaken, because they will be able to
> trigger the installation of the system. Am I correct in this?

Yes, you are correct about this. It is expected to be used as root in the
installation media only.

> Apart from this first look I noticed a few other things:
> 
> - the D-Bus XML configuration is installed into
>   /etc/dbus-1/system.d/org.opensuse.DInstaller.conf, there is an effort to
>   move all these configuration files to /usr/share/dbus-1/system.d instead.
> We
>   should not add new packages with the old path in use.

OK, understood. We are moving this file to /usr/share/dbus-1/system.d. See
https://github.com/yast/d-installer/pull/254.

> - the autostart of the D-Bus service does not seem to work. It is configured
>   in /usr/share/dbus-1/system-services/org.opensuse.DInstaller.service and
>   specifies "SystemdService=d-installer. When attempting to talk to the
>   service without it already running I get the following error though:
> 
>   $ gdbus introspect -y -d org.opensuse.DInstaller -o
> /org/opensuse/DInstaller/Manager1
>   Error: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Unit name
> d-installer is not valid.

Are you trying the service on an already installed system? In the installation
media it seems to work, but I will have a look.

>   After starting the service manually the introspection call works, though.

Regards,
Imo