[Bug 1208394] AUDIT-0: ruby3.1-rubygem-d-installer: follow-up audit of D-Bus setup (separate D-Bus design)
https://bugzilla.suse.com/show_bug.cgi?id=1208394 https://bugzilla.suse.com/show_bug.cgi?id=1208394#c7 --- Comment #7 from Matthias Gerstner <matthias.gerstner@suse.com> --- So from your description in comment 4 it sounds like the addition a D-Bus instance is kind of private to the two containers for backend and the web components. Is that true? Can the UNIX domain socket be accessed from the host system otherwise? Of course the interface of d-installer can be accessed indirectly via the web component, I suppose. Will this listen on localhost or also on remotely accessible network interfaces by default? The separate D-Bus instance only shared by the two containers sounds like it improves the isolation on D-Bus level so I have no problem with that. Although the use of containers on initrd level sounds pretty complex, design wise. What I meant by asking if you are blocked by us is whether you are hitting any whitelisting restrictions that we need to fix? But I don't think so. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com