Bug ID | 1202059 |
---|---|
Summary | AUDIT-0: ruby3.1-rubygem-d-installer: review of D-Bus services org.opensuse.DInstaller (and friends) |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Installation |
Assignee | yast2-maintainers@suse.de |
Reporter | igonzalezsosa@suse.com |
QA Contact | jsrain@suse.com |
Found By | --- |
Blocker | --- |
Hi all, As you might know, we are working on a YaST and web-based experimental installer (https://github.com/yast/d-installer). It uses a set of D-Bus services: * org.opensuse.DInstaller * org.opensuse.DInstaller.Language * org.opensuse.DInstaller.Software * org.opensuse.DInstaller.Users Most probably we are going to add more services in the near future. We have defined them in a D-Bus configuration file: https://github.com/yast/d-installer/blob/master/service/share/dbus.conf (is installed as /etc/dbus-1/system.d/org.opensuse.DInstaller.conf). While trying to submit D-installer to factory, we found out that we need some validation from the security point of view (see https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:adi:19/rubygem-d-installer/standard/x86_64). So my first question is, should we have one D-Bus configuration file per service? If that's the case, I will split services and D-Bus configuration files. Any other comment? Thanks in advance! Regards, Imo